| Author |
Why is deleting an entity that doesn't exist succeeding?
|
Dave Alvarado
Ranch Hand
Joined: Jul 02, 2008
Posts: 434
|
|
Hi,
I'm using JPA 2.0, Hibernate 4.1.0.Final, Spring 3.1.1.RELEASE, and JUnit 4.8.1. I'm confused about why a JUnit test is NOT failing. I have this test
My code for deleting an entity is
Shouldn't the second call to "delete" result in some kind of exception since the entity was removed in the first call? My flush mode is set to AUTO (the default) and below is how I configure my entity manager in my JUnit Spring application context and persistence.xml. Why isn't the second delete call failing?
and here is the persistence.xml file
|
 |
Salil Vverma
Ranch Hand
Joined: Sep 06, 2009
Posts: 219
|
|
Hey Dave,
why should it fail ?
In RDBMS, if you try to delete an non-existing entry from database using sql, database does not throw any exception/error. The statement succeeds with message that zero records impacted. Hibernate provides just a layer on top of database and does not create new behaviors
|
Regards
Salil Verma
|
 |
 |
I agree. Here's the link: jrebel
|
|
subject: Why is deleting an entity that doesn't exist succeeding?
|
|
|