db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig L Russell <Craig.Russ...@Sun.COM>
Subject Negative VOTE Issue 38: New overloaded makeTransient with FetchPlan
Date Mon, 06 Feb 2006 23:25:25 GMT

Please reply if you have objections:

Gives a safe way to make objects transient, possibly to then make  
them persistent in a data store managed by another JDO implementation.
If the user wants to have a hierarchy of objects transient, it's pain  
to go all
over the objects using callbacks or not. An alternative really common  
to use is
detachCopy, but this is expensive because of the objects copies.  
is an alternative less expensive, but it will retain the values for  
all objects
in the transaction which I don't want.

What about a method makeTransient(rootObject, useFetchPlan)?

This method would behave like retrieve(rootObject, true) [FGOnly] in  
terms of loading instances according to the FetchPlan, followed by  
recursive makeTransient on all instances reachable via the fetch plan.


Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!

View raw message