Chris Crossen wrote:
>
> >>If I have object A which has an ArrayList of B objects each of which may
> >>have a collection of C objects, and I commit object A to the database, any
> >>changes made to the B and C objects are automagically reflected to the
> >>database. Modified B and C cause updates, new B and C cause inserts.
> >>
> >>Have I made it clearer?
>
> >The problem is that conceptually, this isn't how Peer's work.
>
> So if we use Peers, we're on our own for managing the hierarchy?
>
That is correct. Another O-R mapping tool is name Osage and can be
found at SourceForge. It started out as a Turbine project, but the
integration never completed and one of the main contributors took the
project off on its own. It is a more complete O-R mapping layer, but I
do not know its current condition.
John McNally
> Chris
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
