| Key: |
JDO-235
|
| Type: |
New Feature
|
| Status: |
Closed
|
| Resolution: |
Duplicate
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Michelle Caisse
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
10/Dec/05 10:01 AM
|
|
A5.6.2-6 [ 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. The persistent-nontransactional-dirty instances will transition according to the RetainValues flag. With the RetainValues flag set to true, persistent-nontransactional-dirty instances will transition to persistent-nontransactional. With the RetainValues flag set to false, persistent-nontransactional-dirty instances will transition to hollow. ]
|
|
Description
|
A5.6.2-6 [ 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. The persistent-nontransactional-dirty instances will transition according to the RetainValues flag. With the RetainValues flag set to true, persistent-nontransactional-dirty instances will transition to persistent-nontransactional. With the RetainValues flag set to false, persistent-nontransactional-dirty instances will transition to hollow. ] |
Show » |
| There are no subversion log entries for this issue yet.
|
|
New test for A5.6.2-6: 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
