Hi,

I wondered if I can get more Information about the object that caused
an Exception when flushing a session.

This may occur when flush() modifies more than one object (e.g. when cascading operations). To get information about the object i have to
"parse" the exeption text.

To act more accurate on Exceptions somtehing like could return the wrong object.

At the time, the only chance to get this Information is to flush()
after every change. But this avoids the advantage to let Hibernate perform
the right order of updates.

Has someone any solutions in mind?

Thanks,

Jens

I'm not sure this is doable.
An exception can occurs because of previous updates on other objects (in the same flush), but we can't manage it since it's an SQL work and error.
so returning the offending object might not be appropriate.