Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Date: Sun, 5 Feb 2012 16:03:54 +0000 (UTC)
From: "Michael Bouschen (Updated) (JIRA)" <jira@apache.org>
To: jdo-dev@db.apache.org
Message-ID: 
 <1418682689.13093.1328457834536.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <321577632.55764.1313843967151.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (JDO-682) Change datastore-identity strategy for
 shoppingcart pc classes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Michael Bouschen updated JDO-682:
---------------------------------

    Description: 
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.


  was:
The datastoreidentity "detach" test use the shoppingcart pc classes. They are mapped uisng the datastore identity strategy increment (see package-standard8.orm):
  <datastore-identity strategy="increment" column="DATASTORE_ID"/>
The strategy should be change 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.


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