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

Christian Bauer (JIRA) noreply at atlassian.com
Thu Feb 22 17:20:31 EST 2007


    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2439?page=comments#action_26228 ] 

Christian Bauer commented on HHH-2439:
--------------------------------------

This is risky, it might break existing applications.

If applications rely on a non-null identifier value being available on an entity instance if its in persistent state, this guarantee no longer holds if they run with FlushMode.MANUAL. Limiting this behavior to the new persist() method _and_ requiring auto-commit mode is a good way of restricting exposure of this behavior to new applications, and to let only users who understand the behavior actually utilize it (we hope).


> 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
>         Type: Improvement

>   Components: core
>     Reporter: Steve Ebersole
>     Assignee: Steve Ebersole
>      Fix For: 3.2.3

>
>
> 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




More information about the hibernate-issues mailing list