Write tests for new persistent-nontransactional-dirty behavior assertions

• Key: JDO-259
• Type: Test
• Status: Resolved
• Resolution: Fixed
• Priority: Major
• Assignee: Craig Russell
• Reporter: Michelle Caisse
• Component/s: tck2
• Affects Version/s: JDO 2 beta
• Fix Version/s: JDO 2 final

Description

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. ]

Comments

[Matthew T. Adams]

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.

[Matthew T. Adams]

As per previous comment.

[Michael Bouschen]

Reopened.
The title is misleading: it talks about detach/attach where the issue is about persistent-nontransactional-dirty.

[Craig Russell]

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.

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.

[Craig Russell]

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.