Hi all,
I've experienced a problem: in a single transaction I deleted an object and created a new one with a different id but with a field that duplicates one of the old object, on which ther's a UNIQUE constraint on the DB.
This shouldn't be a problem, since I'm removing the old object, but Hibernates doesn't executes DML in the same order they're execute, so the insert is executed before the delete.
I know I can use flush() method to force the execution of the delete, but I'm wondering if there's a better solution.
[/u]