[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-609?page=co... ] Suji Suresh commented on ANN-609: --------------------------------- Why is this a new feature and not a bug? I think this is a bug because Hibernate does support this feature plus there is a way to specify "unsaved-value" via the mapping file. There is a way to specify "unsaved-value" via xdoclet in Hibernate2. My project just migrated to Hibernate3/annotations and now all of a sudden the functionality is broken. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-609?page=co... ] Christian Bauer commented on ANN-609: ------------------------------------- And, by the way, marking it as "bug" or "feature" does not really influence when or if someone on our side will write the code for you. Your best bet is to implement the annotation yourself and to submit a patch. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-609?page=co... ] Suji Suresh commented on ANN-609: --------------------------------- The unsaved-value strategy is absolutely necessary for objects that have the primary key value assigned otherwise there is no way for Hibernate to tell the difference between a new object from an existing object and therefore it throws a StaleStateException instead of DataIntegrityViolationException. This is because Hibernate uses the default unsaved-value strategy which a non-null value on the primary key field. In my case where I assign the value for the primary key before passing it on to Hibernate, the primary key field is never null so Hibernate always assumes that it is an existing object and therefore tries to merge with an existing object in the database and if the object is already present in the database it throws a StaleStateException because the value of "row version" field is lesser than the value present in the database. Consider Object A that has a primary key field "id". Object A also has a "rowVersion" field. I give Hibernate a new Object A "a" with id value 123 and rowVersion 0. Hibernate assigns a rowVersion 1 and adds this object no problem. Now I give Hibernate another Object A "a1" with id value 123 and rowVersion 0. Hibernate attempts to add this object but instead finds another Object A with a rowVersion greater than a1's rowVersion and fails with StaleStateException. Now this same usecase will work just fine if I attach an "unsaved-value" of -1 to the rowVersion. This will allow Hibernate to distinguish between a new object (the object with rowVersion -1) from an existing object (an object with rowVersion greater than 0) I hope I was able to clarify my problem -- 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

[ https://hibernate.onjira.com/browse/HHH-4324?page=com.atlassian.jira.plug... ] Gail Badner commented on HHH-4324: ---------------------------------- I believe this issue is out of date. Is anyone still having problems with this? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira