Re: allegro cl installer -- A.I built in, all the way DOWN

Alex Mizrahi wrote:
(message (Hello 'Rainer)
(you :wrote :on '(Sun, 29 Oct 2006 13:19:33 +0200))
(

RJ> I'm not sure if it completely broken by design. That's a dubious claim.

but how do i use standard SQL feature 'on delete cascade' with it then? i don't see such option there.
without that feature database can get inconsistent. the whole point of RDBMS is to make user data ever-consistent.
no one wants to have 'hanging' employees when you delete a company they belong to, or some hanging 'employee-salary' when you delete that employee.

The cascade delete should be part of your database definition (DDL).

Once the RDBMS database is properly defined (including the cascade deletes), every time you issue a
SQL DELETE company WHERE ...
the appropriate company tuple will be deleted and all dependent employee tuples will be deleted.

IOW this has nothing to do with the language or the language implementation but with the RDBMS chosen.
.