db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Jefferson (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JDO-682) Change datastore-identity strategy for shoppingcart pc classes
Date Tue, 28 Feb 2012 14:17:46 GMT

    [ https://issues.apache.org/jira/browse/JDO-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13218203#comment-13218203
] 

Andy Jefferson commented on JDO-682:
------------------------------------

Patch looks fine and, when TCK is run against current DataNucleus, passes. parent pom.xml
was updated to use latest DN jars yesterday.
                
> Change datastore-identity strategy for shoppingcart pc classes
> --------------------------------------------------------------
>
>                 Key: JDO-682
>                 URL: https://issues.apache.org/jira/browse/JDO-682
>             Project: JDO
>          Issue Type: Improvement
>          Components: tck
>    Affects Versions: JDO 3 (3.0)
>            Reporter: Michael Bouschen
>            Assignee: Michael Bouschen
>             Fix For: JDO 3 maintenance release 1 (3.1)
>
>         Attachments: JDO-682.patch
>
>
> The datastoreidentity "detach" test use the shoppingcart pc classes. They are mapped
using the datastore identity strategy increment (see package-standard8.orm):
>   <datastore-identity strategy="increment" column="DATASTORE_ID"/>
> The strategy should be changed to sequence to avoid creating schema dynamically. With
the sequence strategy the name of the sequence can be specified in the metadata. This allows
to create the sequence table as part of the schema creation phase. The tck is designed to
craete the entire schema upfront, such that a JDO implementaion w/o dynamic schema creation/modification
is able to pass the tck. 
> The goal is to avoid using the increment strategy pending resolution of requirements
for increment.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message