[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-5218) Provide a new "pooled value" based optimizer which interprets the database value as the low boundary instead of upper boundary

[Steve Ebersole (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Ebersole closed HHH-5218.
-------------------------------


> Provide a new "pooled value" based optimizer which interprets the database value as the low boundary instead of upper boundary
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HHH-5218
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5218
>             Project: Hibernate Core
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.2.6
>            Reporter: Steve Ebersole
>            Assignee: Steve Ebersole
>             Fix For: 3.5.2, 3.6
>
>          Time Spent: 3h 11m
>  Remaining Estimate: 0h
>
> Splitting up HHH-3608 into its individual tasks.  This part deals with the assumption made in PooledOptimizer that the sequence value is the upper boundary of the current range of values.  This is an assumption and the other assumption that the value is the lower boundary is just as valid, so provide for both by adding a new optimizer.  The new optimizer class will be org.hibernate.id.enhanced.OptimizerFactory.PooledLoOptimizer and its short name will be "pooled-lo".  The already existing one will remain the default, but I will add a config option to allow users to specify which to use per setup ('hibernate.id.prefer_pooling_lo_values').

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