This one time, at band camp, Kvidera, Douglas said:
KD>In the mapping file, classes B and C "depends" on A. For the many-to-many
KD>association between B and C, the association table is mapped to the
KD>C_A_Assoc class (which doesn't "depends"). Class C then implements
KD>jdoAfterCreate() and attempts to create() the appropriate C_A_Assoc objects
KD>therein. When I do:
...
KD>And, yes, I ran the update transaction code on a clean database. It seems
KD>Castor tries to reuse the identity of the association object create()d in
KD>jdoAfterCreate() or the identity of the C object just created. This happens
KD>if the object is created as a result of being added to a parent object that
KD>is updated, but not if the object is created during its parent's creation.
Doug,
Why are you manually handling the many-to-many using a callback?
If the relationships between objects are mapped correctly, Castor
should handle it on its own.
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
