| Craig L Russell 2005-10-23, 5:46 pm |
| Javadogs,
I'd like to get feedback from jdo vendors who have implemented detach
and attach. I'm really keen on getting user feedback or use-cases for
attach.
In particular, how do implementations handle transient instances? Are
there use-cases that demand that transient instances are copied? This
would be the case if the same transient instance was intended to be
attached to multiple persistence managers.
Please let's hear from you.
Thanks,
Craig
P.S. If we agree to remove attachCopy, there are still some questions.
1. What do we do about the "makeTransactional" boolean flag on
attachCopy? Do we automatically make the attached instances
transactional? That is, default the flag to true, or do we add
another variant on makePersistent?
2. What do we do about the attach callbacks? We could preserve them
and just change the documentation to say that the callbacks are
called during makePersistent for detached objects.
On Oct 18, 2005, at 11:21 AM, Wes Biggs wrote:
> I think this is an excellent idea.
>
> I'd be happy to remove the copy semantic on transient instances in
> order to eliminate the need for a separate method. My feeling is
> that transient instances are likely to be retained as references,
> and it's actually less confusing if those references become
> persistent-new.
>
> Wes
>
> Matthew T. Adams wrote:
>
>
>
>
|