[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2439) delay IDENTITY insertions in the case of FlushMode.MANUAL/NEVER

[Paul Benedict (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_30490 ] 

Paul Benedict commented on HHH-2439:
------------------------------------

I hope I didn't miss the finer points, but to what persistence strategy is this issue targeting? Will the delay be applied to both save() and persist()? If it is persist(), then I think it is OKAY, but if the latter then here's my case against it....

The main difference between save() and persist() and is that save() immediately gets an identifier. See HHH-1682 and http://www.hibernate.org/hib_docs/v3/reference/en/html/objectstate.html#objectstate-makingpersistent, which clearly detail the difference: "If Cat has a generated identifier, the identifier is generated and assigned to the cat when save() is called. "



> delay IDENTITY insertions in the case of FlushMode.MANUAL/NEVER
> ---------------------------------------------------------------
>
>                 Key: HHH-2439
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2439
>             Project: Hibernate3
>          Issue Type: Improvement
>          Components: core
>            Reporter: Steve Ebersole
>            Assignee: Steve Ebersole
>             Fix For: 3.3.x
>
>
> Much like we do now in 3.2 for out of transaction operations, we should delay performing insertions for post-insert generators with FlushMode.isManualFlushMode

-- 
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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira