[EMAIL PROTECTED] wrote:
I've always (in OJB ODMG) used cascading delete bounded by appropriate auto-delete settings; now it looks as if I have no choice but to delete each individual object by hand. True? Setting the cascading delete settings by relationship type (1:1, 1:n, m:n) seems extremely weird, and certainly won't be very useful, since the correct delete semantics are always a function of the particular relationship, not of the form of the relationship.

Armin has fixed a number of bugs in OJB in the ODMG area, so ODMG should generally be much more stable in 1.0.3 than 1.0.0.

However, I believe some bugfixes had to be made on the expense of
modified configuration defaults. Especially for the auto-xxx settings
in the repository file.

Armin will have more info on this, but please have a look at the
docs and see if you get past your upgrade frustration:
 http://db.apache.org/ojb/docu/guides/repository.html

See especially:
 class-descriptor
   The accept-locks attribute specifies whether implicit locking should
    propagate to this class. Currently relevant for the ODMG layer only.

 reference-descriptor
   auto-update
     For ODMG-api none is mandatory (since OJB 1.0.2).
   auto-delete
     For ODMG-api none is mandatory (since OJB 1.0.2).

 collection-descriptor
   auto-update
     For ODMG-api none is mandatory (since OJB 1.0.2).


All changed/required settings sould also be self-documented in the repository.dtd comments. Be sure to upgrade repository.dtd, repository-internal.xml, OJB.properties and OJB-logging.properties between releases.

Regards,
 Martin

P.S. I fully agree with you that changed config defaults between minor
releases should generally be avoided. In this case I think some bugs
were considered harmful enough to motivate the frustration...

We should also improve the website with migration HOWTO:s for releases
to avoid the effort to discover this the hard way, like you did.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to