Re: Unknown SQL

>> OODBMSs use garbage collection, however, and Carl was trying to
>> make a claim that garbage collection is easier or more intuitive than
>> cascading deletes.
>
>You are interpreting more into my posting than I was trying to say.

In that case, your posting was pointless on the face of it.

>> In an OODBMS, the DBMS will not delete the
>> enrollment until all the references to it are gone. IE. one must delete
>> both the student and the class before the enrollment disappears.
>
>We are just about to release a callback interface for cascading deletes.

And this is supposed to be simpler than just declaring a cascading delete? LOL Add Callback to the list of concepts your users must learn and understand. Add it to the list of physical implementation details your product exposes in the logical interface to the user.

When someone decides to switch to a different vendor's OODBMS, how do you propose they transport constraint meta-data obfuscated in a procedural callback function?

Regards,
Bob Received on Sun Jul 22 2001 - 01:28:26 CEST