more info requested for "org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect)" ------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-5959 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5959 Project: Hibernate Core Issue Type: Bug Reporter: Derrick Aubin Priority: Minor I just went through a drama with a StaleObjectException, when there was absolutely concurrent access to the database. It turns out that somebody had nulled out the version field in the table in question. Could Hibernate provide some more info in the StaleObjectException, perhaps adding "Check the values of your version field" or better, provide the values of the conflicting version fields? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira