Brian> - odmg-api: Creation of m:n relation only works when
Brian> objects created step by step (or use PB-api as workaround),
Brian> persist a whole object graph doesn't work. On delete of
Brian> collection objects from a m:n relation objects will be
Brian> deleted from the indirection table and (unexpected
Brian> behaviour) from the referenced table too.
me> Also unsure about the deletion piece: Does this mean that
me> auto-delete="link" doesn't work with ODMG any more (it's been
me> working ok in RC6)?
Armin> hmm, at all times the top-level api need the default values
Armin> for auto-xxx settings:
Armin> auto-retrieve true
Armin> auto-update false
Armin> auto-delete false
Armin> But except for auto-delete on 1:1 relation, 'false' is
Armin> equals with 'link'.
Oops. I shouldn't have brought in auto-delete. It sounds from the
release notes like there's a new behavior where removing an object
from an m:n relation removes the object from the db, as well. Is this
only with RemovalAwareCollection (in which case I think it's
expected?), or is this with all collection classes (in which case I
think it's a new behavior and very seriously broken)?
thanks,
--
Steve Clark
Technology Applications Team
Natural Resources Research Center/USGS
[EMAIL PROTECTED]
(970)226-9291
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]