Hibernate to ignore the Objects that were deleted elsewhere?

KC · **Joined:** Tue Oct 21, 2003 3:00 am **Posts:** 11

The problem happens when I have two clients running against a single database. Suppose the database only has one table and two rows:

TABLE
--------
ROW 1
ROW 2

Both client loaded same set of data. After client 1 deleted "ROW 1", client 2 then updates "ROW 2" and attempt to save. As a result I get an "Row not found" exception.

I guess my question is how do I get Hibernate to ignore that "ROW 1" was deleted by someone else and don't throw the exception?

I have looked into the method

Code:

public void delete(Object object) throws HibernateException;

inside SessionImpl class and noticed the following code:

Code:

if ( entry.status==DELETED || entry.status==GONE ) {
  log.trace("object was already deleted");
  return;
}

But there is no method that allows me to change the status of an entry.
Can someone please help me with this?

Many thanks,
KC

andreas · **Posted:** Mon Nov 17, 2003 5:18 am

Why should there be no exception thrown? Isn't it important for client 2 to see, that the row was deleted?

emmanuel · **Posted:** Mon Nov 17, 2003 6:21 am

You must catch the exception and do a save.
This is fundamentaly inconsistent to update an already deleted object/row.
Hibernate manage it correctly.

KC · **Joined:** Tue Oct 21, 2003 3:00 am **Posts:** 11

andreas wrote:

Why should there be no exception thrown? Isn't it important for client 2 to see, that the row was deleted?

In our case, it is perfectly ok to ignore this problem. Having the exception thrown only breaks the flow of the software.

KC · **Joined:** Tue Oct 21, 2003 3:00 am **Posts:** 11

epbernard wrote:

You must catch the exception and do a save.
This is fundamentaly inconsistent to update an already deleted object/row.
Hibernate manage it correctly.

Where should I catch the exception so the flow of the system will not be borken?