[
https://issues.apache.org/jira/browse/JDO-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528904
]
Chris Beams commented on JDO-522:
---------------------------------
The javadoc for both PM and PMF setCopyOnAttach() methods includes:
+ * With this flag set to <code>false</code>, detached parameter
+ * instances are attached directly and change their state from
+ * detached to persistent-clean and from detached-dirty to
+ * persistent-dirty.
I believe it would be clearer if it read "from detached-clean to
persistent-clean", instead of "from detached to persistent-clean"
> Draft proposal for CopyOnAttach property
> ----------------------------------------
>
> Key: JDO-522
> URL: https://issues.apache.org/jira/browse/JDO-522
> Project: JDO
> Issue Type: Task
> Components: api2
> Affects Versions: JDO 2 maintenance release 1
> Environment: n/a
> Reporter: Chris Beams
> Assignee: Chris Beams
> Fix For: JDO 2 maintenance release 1
>
> Attachments: CopyOnAttachWithDetachAllOnCommit.jpg, jdo-522.patch,
> proposal-CopyOnAttach-draft2.rtf, proposal-CopyOnAttach.rtf
>
>
> Minutes: JDO TCK Conference Call Friday, Aug 10, 9 am PDT
> On 8/10/07, Craig L Russell <[EMAIL PROTECTED]> wrote:
> Attendees: Chris Beams, Matthew Adams, Michelle Caisse, Craig Russell
> Agenda:
> 3. Attach (makePersistent) a detached instance always merges changes
> into the cache. Can this behavior be changed to make the parameter
> instance change its state, throwing an exception if there already is
> an instance in the cache, based on a user-specified property? Seems
> like this would be a good addition to the spec. AI Chris prepare a
> proposal for the jdo expert group alias.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
