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/09 06:13:08 UTC

[jira] Updated: (JDO-233) New test for 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...

     [ http://issues.apache.org/jira/browse/JDO-233?page=all ]

Michelle Caisse updated JDO-233:
--------------------------------

    Component: tck20

> New test for 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...
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: JDO-233
>          URL: http://issues.apache.org/jira/browse/JDO-233
>      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. 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. ]

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