> how about putting your temporary objects into some temporary database?
Seems like an ugly solution.
> Most people would have a temporary database for development where you can do
> anything during development.
This would not be for development it would be for launch.
> Finally, if you don't commit, they won't (stay) persist(ed).
That's the problem. Some objects should be comitted others not within the same context.
Is there a way to add temporary objects to one context, but share them with another?
Elia
----- Original Message -----
From: "McDaniel, Joe R." <mcdanij..igr.org>
To: <cayenne-use..bjectstyle.org>
Sent: Wednesday, June 30, 2004 4:01 PM
Subject: RE: Working with Transient Objects
Since you can have multiple databases, how about putting your temporary
objects into some temporary database? Most people would have a temporary
database for development where you can do anything during development.
Finally, if you don't commit, they won't (stay) persist(ed).
Best,
Joe
This archive was generated by hypermail 2.0.0 : Wed Jun 30 2004 - 11:43:17 EDT