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 "Michelle Caisse (JIRA)" <ji...@apache.org> on 2005/12/10 01:59:07 UTC
[jira] Created: (JDO-259) Write tests for attach/detach behavior assertions
Write tests for attach/detach behavior assertions
-------------------------------------------------
Key: JDO-259
URL: http://issues.apache.org/jira/browse/JDO-259
Project: JDO
Type: New Feature
Components: tck20
Reporter: Michelle Caisse
A5.6.2-4 [If a datastore transaction is begun, commit will write the changes to the datastore with no checking as to the current state of the instances in the datastore. That is, the changes made outside the transaction together with any changes made inside the transaction will overwrite the current state of the datastore.]
A5.6.2-6 [If a datastore transaction is begun, rollback will not write any changes to the datastore.]
A5.6.2-8 [If an optimistic transaction is begun, commit will write the changes to the datastore after checking as to the current state of the instances in the datastore. The changes made outside the transaction together with any changes made inside the transaction will update the current state of the datastore if the version checking is successful.]
A5.6.2-10 [If an optimistic transaction is begun, rollback will not write any changes to the datastore. The persistent-nontransactional-dirty instances will transition according to the RestoreValues flag. ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (JDO-259) Write tests for new
persistent-nontransactional-dirty behavior assertions
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-259?page=all ]
Craig Russell reassigned JDO-259:
---------------------------------
Assign To: (was: Matthew T. Adams)
> Write tests for new persistent-nontransactional-dirty behavior assertions
> -------------------------------------------------------------------------
>
> Key: JDO-259
> URL: http://issues.apache.org/jira/browse/JDO-259
> Project: JDO
> Type: New Feature
> Components: tck20
> Reporter: Michelle Caisse
>
> A5.6.2-4 [If a datastore transaction is begun, commit will write the changes to the datastore with no checking as to the current state of the instances in the datastore. That is, the changes made outside the transaction together with any changes made inside the transaction will overwrite the current state of the datastore.]
> A5.6.2-6 [If a datastore transaction is begun, rollback will not write any changes to the datastore.]
> A5.6.2-8 [If an optimistic transaction is begun, commit will write the changes to the datastore after checking as to the current state of the instances in the datastore. The changes made outside the transaction together with any changes made inside the transaction will update the current state of the datastore if the version checking is successful.]
> A5.6.2-10 [If an optimistic transaction is begun, rollback will not write any changes to the datastore. The persistent-nontransactional-dirty instances will transition according to the RestoreValues flag. ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JDO-259) Write tests for new
persistent-nontransactional-dirty behavior assertions
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-259?page=all ]
Craig Russell updated JDO-259:
------------------------------
Attachment: NontransactionalWriteDatastoreCommitConflict.java
NontransactionalWriteDatastoreRollback.java
> Write tests for new persistent-nontransactional-dirty behavior assertions
> -------------------------------------------------------------------------
>
> Key: JDO-259
> URL: http://issues.apache.org/jira/browse/JDO-259
> Project: JDO
> Type: Test
> Components: tck20
> Versions: JDO 2 beta
> Reporter: Michelle Caisse
> Assignee: Craig Russell
> Fix For: JDO 2 final
> Attachments: NontransactionalWriteDatastoreCommit.java, NontransactionalWriteDatastoreCommitConflict.java, NontransactionalWriteDatastoreRollback.java, NontransactionalWriteTest.java, NontransactionalWriteThrows.java
>
> A5.6.2-4 [If a datastore transaction is begun, commit will write the changes to the datastore with no checking as to the current state of the instances in the datastore. That is, the changes made outside the transaction together with any changes made inside the transaction will overwrite the current state of the datastore.]
> A5.6.2-6 [If a datastore transaction is begun, rollback will not write any changes to the datastore.]
> A5.6.2-8 [If an optimistic transaction is begun, commit will write the changes to the datastore after checking as to the current state of the instances in the datastore. The changes made outside the transaction together with any changes made inside the transaction will update the current state of the datastore if the version checking is successful.]
> A5.6.2-10 [If an optimistic transaction is begun, rollback will not write any changes to the datastore. The persistent-nontransactional-dirty instances will transition according to the RestoreValues flag. ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (JDO-259) Write tests for attach/detach behavior assertions
Posted by "Matthew T. Adams (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-259?page=all ]
Matthew T. Adams reassigned JDO-259:
------------------------------------
Assign To: Matthew T. Adams
> Write tests for attach/detach behavior assertions
> -------------------------------------------------
>
> Key: JDO-259
> URL: http://issues.apache.org/jira/browse/JDO-259
> Project: JDO
> Type: New Feature
> Components: tck20
> Reporter: Michelle Caisse
> Assignee: Matthew T. Adams
>
> A5.6.2-4 [If a datastore transaction is begun, commit will write the changes to the datastore with no checking as to the current state of the instances in the datastore. That is, the changes made outside the transaction together with any changes made inside the transaction will overwrite the current state of the datastore.]
> A5.6.2-6 [If a datastore transaction is begun, rollback will not write any changes to the datastore.]
> A5.6.2-8 [If an optimistic transaction is begun, commit will write the changes to the datastore after checking as to the current state of the instances in the datastore. The changes made outside the transaction together with any changes made inside the transaction will update the current state of the datastore if the version checking is successful.]
> A5.6.2-10 [If an optimistic transaction is begun, rollback will not write any changes to the datastore. The persistent-nontransactional-dirty instances will transition according to the RestoreValues flag. ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JDO-259) Write tests for new
persistent-nontransactional-dirty behavior assertions
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-259?page=all ]
Craig Russell updated JDO-259:
------------------------------
Attachment: NontransactionalWriteOptimisticCommitConflict.java
NontransactionalWriteOptimisticCommit.java
NontransactionalWriteOptimisticRollback.java
> Write tests for new persistent-nontransactional-dirty behavior assertions
> -------------------------------------------------------------------------
>
> Key: JDO-259
> URL: http://issues.apache.org/jira/browse/JDO-259
> Project: JDO
> Type: Test
> Components: tck20
> Versions: JDO 2 beta
> Reporter: Michelle Caisse
> Assignee: Craig Russell
> Fix For: JDO 2 final
> Attachments: NontransactionalWriteDatastoreCommit.java, NontransactionalWriteDatastoreCommitConflict.java, NontransactionalWriteDatastoreRollback.java, NontransactionalWriteOptimisticCommit.java, NontransactionalWriteOptimisticCommitConflict.java, NontransactionalWriteOptimisticRollback.java, NontransactionalWriteTest.java, NontransactionalWriteThrows.java
>
> A5.6.2-4 [If a datastore transaction is begun, commit will write the changes to the datastore with no checking as to the current state of the instances in the datastore. That is, the changes made outside the transaction together with any changes made inside the transaction will overwrite the current state of the datastore.]
> A5.6.2-6 [If a datastore transaction is begun, rollback will not write any changes to the datastore.]
> A5.6.2-8 [If an optimistic transaction is begun, commit will write the changes to the datastore after checking as to the current state of the instances in the datastore. The changes made outside the transaction together with any changes made inside the transaction will update the current state of the datastore if the version checking is successful.]
> A5.6.2-10 [If an optimistic transaction is begun, rollback will not write any changes to the datastore. The persistent-nontransactional-dirty instances will transition according to the RestoreValues flag. ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (JDO-259) Write tests for new
persistent-nontransactional-dirty behavior assertions
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-259?page=all ]
Craig Russell reassigned JDO-259:
---------------------------------
Assign To: Craig Russell
> Write tests for new persistent-nontransactional-dirty behavior assertions
> -------------------------------------------------------------------------
>
> Key: JDO-259
> URL: http://issues.apache.org/jira/browse/JDO-259
> Project: JDO
> Type: Test
> Components: tck20
> Versions: JDO 2 beta
> Reporter: Michelle Caisse
> Assignee: Craig Russell
> Fix For: JDO 2 final
>
> A5.6.2-4 [If a datastore transaction is begun, commit will write the changes to the datastore with no checking as to the current state of the instances in the datastore. That is, the changes made outside the transaction together with any changes made inside the transaction will overwrite the current state of the datastore.]
> A5.6.2-6 [If a datastore transaction is begun, rollback will not write any changes to the datastore.]
> A5.6.2-8 [If an optimistic transaction is begun, commit will write the changes to the datastore after checking as to the current state of the instances in the datastore. The changes made outside the transaction together with any changes made inside the transaction will update the current state of the datastore if the version checking is successful.]
> A5.6.2-10 [If an optimistic transaction is begun, rollback will not write any changes to the datastore. The persistent-nontransactional-dirty instances will transition according to the RestoreValues flag. ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JDO-259) Write tests for new
persistent-nontransactional-dirty behavior assertions
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-259?page=all ]
Craig Russell updated JDO-259:
------------------------------
Fix Version: JDO 2 rc1
Version: JDO 2 beta
> Write tests for new persistent-nontransactional-dirty behavior assertions
> -------------------------------------------------------------------------
>
> Key: JDO-259
> URL: http://issues.apache.org/jira/browse/JDO-259
> Project: JDO
> Type: New Feature
> Components: tck20
> Versions: JDO 2 beta
> Reporter: Michelle Caisse
> Fix For: JDO 2 rc1
>
> A5.6.2-4 [If a datastore transaction is begun, commit will write the changes to the datastore with no checking as to the current state of the instances in the datastore. That is, the changes made outside the transaction together with any changes made inside the transaction will overwrite the current state of the datastore.]
> A5.6.2-6 [If a datastore transaction is begun, rollback will not write any changes to the datastore.]
> A5.6.2-8 [If an optimistic transaction is begun, commit will write the changes to the datastore after checking as to the current state of the instances in the datastore. The changes made outside the transaction together with any changes made inside the transaction will update the current state of the datastore if the version checking is successful.]
> A5.6.2-10 [If an optimistic transaction is begun, rollback will not write any changes to the datastore. The persistent-nontransactional-dirty instances will transition according to the RestoreValues flag. ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JDO-259) Write tests for new
persistent-nontransactional-dirty behavior assertions
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-259?page=all ]
Craig Russell updated JDO-259:
------------------------------
type: Test (was: New Feature)
> Write tests for new persistent-nontransactional-dirty behavior assertions
> -------------------------------------------------------------------------
>
> Key: JDO-259
> URL: http://issues.apache.org/jira/browse/JDO-259
> Project: JDO
> Type: Test
> Components: tck20
> Versions: JDO 2 beta
> Reporter: Michelle Caisse
> Fix For: JDO 2 rc1
>
> A5.6.2-4 [If a datastore transaction is begun, commit will write the changes to the datastore with no checking as to the current state of the instances in the datastore. That is, the changes made outside the transaction together with any changes made inside the transaction will overwrite the current state of the datastore.]
> A5.6.2-6 [If a datastore transaction is begun, rollback will not write any changes to the datastore.]
> A5.6.2-8 [If an optimistic transaction is begun, commit will write the changes to the datastore after checking as to the current state of the instances in the datastore. The changes made outside the transaction together with any changes made inside the transaction will update the current state of the datastore if the version checking is successful.]
> A5.6.2-10 [If an optimistic transaction is begun, rollback will not write any changes to the datastore. The persistent-nontransactional-dirty instances will transition according to the RestoreValues flag. ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JDO-259) Write tests for new
persistent-nontransactional-dirty behavior assertions
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-259?page=all ]
Craig Russell updated JDO-259:
------------------------------
Attachment: NontransactionalWriteTest.java
NontransactionalWriteThrows.java
NontransactionalWriteDatastoreCommit.java
These tests run on JPOX, but JPOX doesn't support NontransactionalWrite. In case there is an issue with one of the tests, I've split the tests into multiple test classes.
> Write tests for new persistent-nontransactional-dirty behavior assertions
> -------------------------------------------------------------------------
>
> Key: JDO-259
> URL: http://issues.apache.org/jira/browse/JDO-259
> Project: JDO
> Type: Test
> Components: tck20
> Versions: JDO 2 beta
> Reporter: Michelle Caisse
> Assignee: Craig Russell
> Fix For: JDO 2 final
> Attachments: NontransactionalWriteDatastoreCommit.java, NontransactionalWriteTest.java, NontransactionalWriteThrows.java
>
> A5.6.2-4 [If a datastore transaction is begun, commit will write the changes to the datastore with no checking as to the current state of the instances in the datastore. That is, the changes made outside the transaction together with any changes made inside the transaction will overwrite the current state of the datastore.]
> A5.6.2-6 [If a datastore transaction is begun, rollback will not write any changes to the datastore.]
> A5.6.2-8 [If an optimistic transaction is begun, commit will write the changes to the datastore after checking as to the current state of the instances in the datastore. The changes made outside the transaction together with any changes made inside the transaction will update the current state of the datastore if the version checking is successful.]
> A5.6.2-10 [If an optimistic transaction is begun, rollback will not write any changes to the datastore. The persistent-nontransactional-dirty instances will transition according to the RestoreValues flag. ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JDO-259) Write tests for new
persistent-nontransactional-dirty behavior assertions
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-259?page=all ]
Michael Bouschen updated JDO-259:
---------------------------------
Summary: Write tests for new persistent-nontransactional-dirty behavior assertions (was: Write tests for attach/detach behavior assertions)
> Write tests for new persistent-nontransactional-dirty behavior assertions
> -------------------------------------------------------------------------
>
> Key: JDO-259
> URL: http://issues.apache.org/jira/browse/JDO-259
> Project: JDO
> Type: New Feature
> Components: tck20
> Reporter: Michelle Caisse
> Assignee: Matthew T. Adams
>
> A5.6.2-4 [If a datastore transaction is begun, commit will write the changes to the datastore with no checking as to the current state of the instances in the datastore. That is, the changes made outside the transaction together with any changes made inside the transaction will overwrite the current state of the datastore.]
> A5.6.2-6 [If a datastore transaction is begun, rollback will not write any changes to the datastore.]
> A5.6.2-8 [If an optimistic transaction is begun, commit will write the changes to the datastore after checking as to the current state of the instances in the datastore. The changes made outside the transaction together with any changes made inside the transaction will update the current state of the datastore if the version checking is successful.]
> A5.6.2-10 [If an optimistic transaction is begun, rollback will not write any changes to the datastore. The persistent-nontransactional-dirty instances will transition according to the RestoreValues flag. ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (JDO-259) Write tests for new
persistent-nontransactional-dirty behavior assertions
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-259?page=all ]
Craig Russell resolved JDO-259:
-------------------------------
Resolution: Fixed
svn commit -m "JDO-259 Added new NontransactionalWrite tests; removed the old test" src/java/org/apache/jdo/tck/lifecycle/NontransactionalWrite* src/java/org/apache/jdo/tck/lifecycle/nontransactional src/java/org/apache/jdo/tck/lifecycle/nontransactional/ModificationOfNontransactionalInstanceOutsideTransaction.java src/conf/lifecycle.conf
Sending src/conf/lifecycle.conf
Adding src/java/org/apache/jdo/tck/lifecycle/NontransactionalWriteDatastoreCommit.java
Adding src/java/org/apache/jdo/tck/lifecycle/NontransactionalWriteDatastoreCommitConflict.java
Adding src/java/org/apache/jdo/tck/lifecycle/NontransactionalWriteDatastoreRollback.java
Adding src/java/org/apache/jdo/tck/lifecycle/NontransactionalWriteOptimisticCommit.java
Adding src/java/org/apache/jdo/tck/lifecycle/NontransactionalWriteOptimisticCommitConflict.java
Adding src/java/org/apache/jdo/tck/lifecycle/NontransactionalWriteOptimisticRollback.java
Adding src/java/org/apache/jdo/tck/lifecycle/NontransactionalWriteTest.java
Adding src/java/org/apache/jdo/tck/lifecycle/NontransactionalWriteThrows.java
Deleting src/java/org/apache/jdo/tck/lifecycle/nontransactional
Transmitting file data .........
Committed revision 386502.
> Write tests for new persistent-nontransactional-dirty behavior assertions
> -------------------------------------------------------------------------
>
> Key: JDO-259
> URL: http://issues.apache.org/jira/browse/JDO-259
> Project: JDO
> Type: Test
> Components: tck20
> Versions: JDO 2 beta
> Reporter: Michelle Caisse
> Assignee: Craig Russell
> Fix For: JDO 2 final
> Attachments: NontransactionalWriteDatastoreCommit.java, NontransactionalWriteDatastoreCommitConflict.java, NontransactionalWriteDatastoreRollback.java, NontransactionalWriteOptimisticCommit.java, NontransactionalWriteOptimisticCommitConflict.java, NontransactionalWriteOptimisticRollback.java, NontransactionalWriteTest.java, NontransactionalWriteThrows.java
>
> A5.6.2-4 [If a datastore transaction is begun, commit will write the changes to the datastore with no checking as to the current state of the instances in the datastore. That is, the changes made outside the transaction together with any changes made inside the transaction will overwrite the current state of the datastore.]
> A5.6.2-6 [If a datastore transaction is begun, rollback will not write any changes to the datastore.]
> A5.6.2-8 [If an optimistic transaction is begun, commit will write the changes to the datastore after checking as to the current state of the instances in the datastore. The changes made outside the transaction together with any changes made inside the transaction will update the current state of the datastore if the version checking is successful.]
> A5.6.2-10 [If an optimistic transaction is begun, rollback will not write any changes to the datastore. The persistent-nontransactional-dirty instances will transition according to the RestoreValues flag. ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (JDO-259) Write tests for new
persistent-nontransactional-dirty behavior assertions
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-259?page=comments#action_12369773 ]
Craig Russell commented on JDO-259:
-----------------------------------
The existing test org.apache.jdo.tck.lifecycle.nontransactionalModificationOfNontransactionalInstanceOutsideTransaction checks the assertion from JDO1:
* With <code>NontransactionalWrite</code> set to <code>true</code>,
* modification of nontransactional persistent instances is permitted outside
* a transaction. The changes do not participate in any subsequent transaction.
This test will be modified for JDO2.
> Write tests for new persistent-nontransactional-dirty behavior assertions
> -------------------------------------------------------------------------
>
> Key: JDO-259
> URL: http://issues.apache.org/jira/browse/JDO-259
> Project: JDO
> Type: Test
> Components: tck20
> Versions: JDO 2 beta
> Reporter: Michelle Caisse
> Assignee: Craig Russell
> Fix For: JDO 2 final
>
> A5.6.2-4 [If a datastore transaction is begun, commit will write the changes to the datastore with no checking as to the current state of the instances in the datastore. That is, the changes made outside the transaction together with any changes made inside the transaction will overwrite the current state of the datastore.]
> A5.6.2-6 [If a datastore transaction is begun, rollback will not write any changes to the datastore.]
> A5.6.2-8 [If an optimistic transaction is begun, commit will write the changes to the datastore after checking as to the current state of the instances in the datastore. The changes made outside the transaction together with any changes made inside the transaction will update the current state of the datastore if the version checking is successful.]
> A5.6.2-10 [If an optimistic transaction is begun, rollback will not write any changes to the datastore. The persistent-nontransactional-dirty instances will transition according to the RestoreValues flag. ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (JDO-259) Write tests for attach/detach behavior assertions
Posted by "Matthew T. Adams (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-259?page=comments#action_12361772 ]
Matthew T. Adams commented on JDO-259:
--------------------------------------
I'm not sure that I see how these assertions have anything to do with attach/detach behaviors. They appear to be more related to the persistent-nontransactional-dirty state. The sections directly relevant to attach/detach are "5.5.8 Detached-clean", "5.5.9 Detached-dirty", and "12.6.8 Detaching and attaching instances".
I'll resolve this issue as "won't fix" and create a new issue for the sections listed above.
> Write tests for attach/detach behavior assertions
> -------------------------------------------------
>
> Key: JDO-259
> URL: http://issues.apache.org/jira/browse/JDO-259
> Project: JDO
> Type: New Feature
> Components: tck20
> Reporter: Michelle Caisse
> Assignee: Matthew T. Adams
>
> A5.6.2-4 [If a datastore transaction is begun, commit will write the changes to the datastore with no checking as to the current state of the instances in the datastore. That is, the changes made outside the transaction together with any changes made inside the transaction will overwrite the current state of the datastore.]
> A5.6.2-6 [If a datastore transaction is begun, rollback will not write any changes to the datastore.]
> A5.6.2-8 [If an optimistic transaction is begun, commit will write the changes to the datastore after checking as to the current state of the instances in the datastore. The changes made outside the transaction together with any changes made inside the transaction will update the current state of the datastore if the version checking is successful.]
> A5.6.2-10 [If an optimistic transaction is begun, rollback will not write any changes to the datastore. The persistent-nontransactional-dirty instances will transition according to the RestoreValues flag. ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Reopened: (JDO-259) Write tests for attach/detach behavior
assertions
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-259?page=all ]
Michael Bouschen reopened JDO-259:
----------------------------------
Reopened.
The title is misleading: it talks about detach/attach where the issue is about persistent-nontransactional-dirty.
> Write tests for attach/detach behavior assertions
> -------------------------------------------------
>
> Key: JDO-259
> URL: http://issues.apache.org/jira/browse/JDO-259
> Project: JDO
> Type: New Feature
> Components: tck20
> Reporter: Michelle Caisse
> Assignee: Matthew T. Adams
>
> A5.6.2-4 [If a datastore transaction is begun, commit will write the changes to the datastore with no checking as to the current state of the instances in the datastore. That is, the changes made outside the transaction together with any changes made inside the transaction will overwrite the current state of the datastore.]
> A5.6.2-6 [If a datastore transaction is begun, rollback will not write any changes to the datastore.]
> A5.6.2-8 [If an optimistic transaction is begun, commit will write the changes to the datastore after checking as to the current state of the instances in the datastore. The changes made outside the transaction together with any changes made inside the transaction will update the current state of the datastore if the version checking is successful.]
> A5.6.2-10 [If an optimistic transaction is begun, rollback will not write any changes to the datastore. The persistent-nontransactional-dirty instances will transition according to the RestoreValues flag. ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (JDO-259) Write tests for attach/detach behavior assertions
Posted by "Matthew T. Adams (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-259?page=all ]
Matthew T. Adams resolved JDO-259:
----------------------------------
Resolution: Won't Fix
As per previous comment.
> Write tests for attach/detach behavior assertions
> -------------------------------------------------
>
> Key: JDO-259
> URL: http://issues.apache.org/jira/browse/JDO-259
> Project: JDO
> Type: New Feature
> Components: tck20
> Reporter: Michelle Caisse
> Assignee: Matthew T. Adams
>
> A5.6.2-4 [If a datastore transaction is begun, commit will write the changes to the datastore with no checking as to the current state of the instances in the datastore. That is, the changes made outside the transaction together with any changes made inside the transaction will overwrite the current state of the datastore.]
> A5.6.2-6 [If a datastore transaction is begun, rollback will not write any changes to the datastore.]
> A5.6.2-8 [If an optimistic transaction is begun, commit will write the changes to the datastore after checking as to the current state of the instances in the datastore. The changes made outside the transaction together with any changes made inside the transaction will update the current state of the datastore if the version checking is successful.]
> A5.6.2-10 [If an optimistic transaction is begun, rollback will not write any changes to the datastore. The persistent-nontransactional-dirty instances will transition according to the RestoreValues flag. ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JDO-259) Write tests for new
persistent-nontransactional-dirty behavior assertions
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-259?page=all ]
Craig Russell updated JDO-259:
------------------------------
Fix Version: JDO 2 final
(was: JDO 2 rc1)
> Write tests for new persistent-nontransactional-dirty behavior assertions
> -------------------------------------------------------------------------
>
> Key: JDO-259
> URL: http://issues.apache.org/jira/browse/JDO-259
> Project: JDO
> Type: Test
> Components: tck20
> Versions: JDO 2 beta
> Reporter: Michelle Caisse
> Fix For: JDO 2 final
>
> A5.6.2-4 [If a datastore transaction is begun, commit will write the changes to the datastore with no checking as to the current state of the instances in the datastore. That is, the changes made outside the transaction together with any changes made inside the transaction will overwrite the current state of the datastore.]
> A5.6.2-6 [If a datastore transaction is begun, rollback will not write any changes to the datastore.]
> A5.6.2-8 [If an optimistic transaction is begun, commit will write the changes to the datastore after checking as to the current state of the instances in the datastore. The changes made outside the transaction together with any changes made inside the transaction will update the current state of the datastore if the version checking is successful.]
> A5.6.2-10 [If an optimistic transaction is begun, rollback will not write any changes to the datastore. The persistent-nontransactional-dirty instances will transition according to the RestoreValues flag. ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira