[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1682) Improve the description of differences between save() and persist()

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1682?page=c... ] Diego Pires Plentz commented on HHH-1682: ----------------------------------------- I found that a lot of people have the same doubt. To help to solve this issue I'm quoting Christian Bauer: "In case anybody finds this thread... persist() is well defined. It makes a transient instance persistent. However, it doesn't guarantee that the identifier value will be assigned to the persistent instance immediately, the assignment might happen at flush time. The spec doesn't say that, which is the problem I have with persist(). persist() also guarantees that it will not execute an INSERT statement if it is called outside of transaction boundaries. This is useful in long-running conversations with an extended Session/persistence context. A method like persist() is required. save() does not guarantee the same, it returns an identifier, and if an INSERT has to be executed to get the identifier (e.g. "identity" generator, not "sequence"), this INSERT happens immediately, no matter if you are inside or outside of a transaction. This is not good in a long-running conversation with an extended Session/persistence context." http://forum.hibernate.org/viewtopic.php?p=2325758&sid=a69cf62ab04516... http://opensource.atlassian.com/projects/hibernate/browse/HHH-1273#action... -- 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