Hey,

I know we're a bit running behind, but we want to upgrade Hibernate from 3.2.0.cr1 to 3.5.6. We already encountered some small issues, but this one is rather important:

Apparently, the default behavior for deleting an object has been altered. We currently use following scenario in a bunch of our front-end applications:

- session1 loads the object
- display the object on screen
- user presses the delete-button
- session2 performs the actual delete

You see that we detach the object & then delete it. This still works OK in normal situations, but we notice that Hibernate now first tries to select the object before deleting it. This not only performs a useless query, but we get different results if the object was actually not found:

- 3.2.0.cr1: we get a StaleStateException (org.hibernate.StaleStateException: Unexpected row count: 0 expected: 1)
- 3.5.6: the delete simply does nothing, as he didn't found the object in the select, it simply returns

Although it may not be the best way of doing it, several of our applications rely on the fact that this would throw an exception. Is there a config/workaround for this issue?

We're still using a HibernateTemplate, so in the worst case, I could write something around the delete-function to alter the behavior if the session doesn't contain the object yet.. But this is far from ideal.

Thanks in advance,

Sven

Hi again,


First of all, happy holidays to everyone.. :)

Hasn't anyone experienced the same issues when upgrading Hibernate in a working environment? How did you guys tackle this issue?

*edit*: some other discussion on +- this issue: http://stackoverflow.com/questions/13210638/hibernate-delete-query
-> I understand why Hibernate does that, it's quite logic. However, it is not backwards compatible as it doesn't throw the exception, so for our production environment, this is currently a stopper.


Thanks,

Sven

Hey again,

What do you guys think of following work-around? Is it safe enough to implement?

I noticed the extra select-query is triggered in the DefaultDeleteEventListener.onDelete(DeleteEvent event, Set transientEntities):



So I made a CustomDeleteEventListener which extends the DefaultDeleteEventListener & overrides following method:



Thanks,

Sven