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 "Chris Beams (JIRA)" <ji...@apache.org> on 2007/09/14 07:58:32 UTC
[jira] Updated: (JDO-522) Draft proposal for CopyOnAttach property
[ https://issues.apache.org/jira/browse/JDO-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Beams updated JDO-522:
----------------------------
Attachment: proposal-CopyOnAttach.rtf
Per the email I just sent out to the jdo-dev list, attaching the first draft proposal for a new CopyOnAttach property.
> 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: proposal-CopyOnAttach.rtf
>
>
> Minutes: JDO TCK Conference Call Friday, Aug 10, 9 am PDT
> On 8/10/07, Craig L Russell <Cr...@sun.com> 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.