openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yves (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENJPA-1376) @GeneratedValue allocationSize incorrect implementation
Date Wed, 04 Nov 2009 23:51:32 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yves updated OPENJPA-1376:
--------------------------

    Remaining Estimate: 8h  (was: 0.13h)
     Original Estimate: 8h  (was: 0.13h)

> @GeneratedValue allocationSize incorrect implementation
> -------------------------------------------------------
>
>                 Key: OPENJPA-1376
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1376
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 1.2.1, 2.0.0-M3
>         Environment: All
>            Reporter: Yves
>            Priority: Critical
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> OpenJpa use allocationSize parameter on NativeJDBCSeq to set the sequence cache value.
> But one "JSR 220: Enterprise JavaBeansTM,Version 3.0" , the allocationSize is : "The
amount to increment by when allocating sequence
> numbers from the sequence."
> Allocating is used to limit the number of access to the sequence or table not to set
the sequence cache value !
> If allocationSize=50, the sequence need to be call one time on each 50 call on AbstractJDBCSeq.next().
> 1 call on AbstractJDBCSeq.next(). call the sequence or table 
> 2 call : return previous value + 1;
> 3 call : return previous value + 2;
> ...
> 51 call :re-call the sequence
> 52 return previous value + 1
> ...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message