Need help with Hibernate? Read this first:
http://www.hibernate.org/ForumMailingli ... AskForHelp

Hibernate version:3.2.5ga

Mapping documents:not relevant

Code between sessionFactory.openSession() and session.close():

Code:

session.save(newObject);
session.refresh(newObject); //needed because a trigger is involved
...
session.flush();

Full stack trace of any exception that occurs:
HibernateException: this instance does not yet exist as a row in the database


Name and version of the database you are using:
Oracl10g



Hi,

I switched from Hibernate 3.1.2 to 3.2.5ga. The above code snippet worked in version 3.1.2. After upgrading to 3.2.5ga I get the HibernateException: this instance does not yet exist as a row in the database.

When I remove it works. However I need to refresh the object because a trigger on the database added some values.

Why does Hibernate 3.2.5ga behaves differently in comparison to 3.1.2?! Has something changed which I have to consider?

greetings,
Tina

Try putting the session.flush() after the save() and before the reset(). Hibernate uses delayed inserts/updates whenever it thinks it can. flush() forces it to write everything that is marked as new or dirty to the database.

Another option would be to marked the columns which your trigger updates as 'generated'. That should make the save() execute immediately and the refresh() unnecessary.

thanks for your answer. I have tried both options and now I am getting the error message "the row with the given identifier does not exist".

This is really strange because we did not change anything to the code or mappings and all works well with the prior Hibernate 3.1.2.

Sorry you had no success with my suggestions. I have no idea what has changed between 3.1 and 3.2. The error message seems to indicate Hibernate has problems locating the saved object. Are you using a database generated primary key or an application provided primary key? If it is a database generated primary key something must have gone wrong with getting it back into your object. If you can't step through your application with a debugger add a log statement which logs the relevant fields from your newObject. Also enable Hibernate statement logging and check what is actually submitted to the database.