[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-2471) create a set of "enhanced" generators

Steve Ebersole (JIRA) noreply at atlassian.com
Tue Mar 20 22:59:09 EDT 2007


     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2471?page=all ]
     
Steve Ebersole closed HHH-2471:
-------------------------------

    Resolution: Fixed

Added:
(1) org.hibernate.id.enhanced.SequenceStyleGenerator
(2) org.hibernate.id.enhanced.TableGenerator

Would eventually like for (1) to replace org.hibernate.id.SequenceGenerator for "sequence" and (2) to replace org.hibernate.id.TableGenerator for "table".   The second replacement might be problematic for user actually using the current org.hibernate.id.TableGenerator directly, which however is/was never encouraged.

> create a set of "enhanced" generators
> -------------------------------------
>
>          Key: HHH-2471
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2471
>      Project: Hibernate3
>         Type: New Feature

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

>
>
> Specifically, the build the following two capabilities:
> 1) a sequence "style" generator targetting cross db portability in a better fashion that native.  specifically, use sequences if dialect supports them; otherwise fall back to a table-based implementation *with the same characteristics*.
> 2) ability to easily apply "optimizations" without needing to create a whole new generator.  by optimizations i mean wrapping in a hilo or "pooled" algorithm.
> This will result in two new generators:
> 1) SequenceStyleGenerator
> 2) SegmentedTableGenerator (better names welcome)
> Specifically, SequenceStyleGenerator by itself fulfills requirement #1.  It does also accept pluggable optimizers.
> SegmentedTableGenerator is to be a rewrite of the current MultiTableHiLoGenerator which performs the same basic function as MultiTableHiLoGenerator in terms of table layout in order to store multiple (or segmented) sequences.  However, it will also take advantage of the pluggable optimizers.

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