You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Michael Bouschen (JIRA)" <ji...@apache.org> on 2011/08/20 14:39:27 UTC
[jira] [Created] (JDO-682) Change datastore-identity strategy for
shoppingcart pc classes
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
Reporter: Michael Bouschen
Assignee: Michael Bouschen
Fix For: JDO 3 maintenance release 1
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-682) Change datastore-identity strategy for
shoppingcart pc classes
Posted by "Andy Jefferson (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (JDO-682) Change datastore-identity strategy for
shoppingcart pc classes
Posted by "Michael Bouschen (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Bouschen updated JDO-682:
---------------------------------
Attachment: JDO-682.patch
The attached patch JDO-682.patch changes the schema datastoreidentity/schema8.sql to create a sequence and the mapping package-standard8.orm of the shoppingcart pc classes to use a sequence.
See http://www.datanucleus.org/servlet/jira/browse/NUCRDBMS-581 for the corresponding DN support.
> 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
[jira] [Resolved] (JDO-682) Change datastore-identity strategy for
shoppingcart pc classes
Posted by "Michael Bouschen (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Bouschen resolved JDO-682.
----------------------------------
Resolution: Fixed
Thanks for updating the dependency.
Checked in the patch (see revision 1295288).
> 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
[jira] [Updated] (JDO-682) Change datastore-identity strategy for
shoppingcart pc classes
Posted by "Michael Bouschen (Updated) (JIRA)" <ji...@apache.org>.
[ 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