Re: Requirements for update languages?

"David Cressey" <david_at_dcressey.com> wrote in message news:5W5C9.276$0I3.28179_at_petpeeve.ziplink.net...
> > None of them make cascaded actions directly visible to the users (although
> I
> > guess users could read the calalog and parse their own statements, adding
> in
> > any cascaded actions themselves, but that is hardly what I'm trying to get
> at)
>
> I must be misunderstanding what you are saying. If a user deletes a parent,
> say invoice header with invoice number 12345, and this triggers a cascaded
> delete of invoice items with the same invoice number, and then, in the
> context of the same transaction, the user queries for invoice items with the
> same invoice number yet again, the system should respond with an empty
> result. No?

Yes.

> Or is this not what you mean?

Indeed it is not. What I am saying is that the user should be able to see that the statement that actually got executed in his name was.

    InvoiceHeader := InvioceHeader MINUS (InvoiceHeader WHERE InvNo = 12345),     InvoiceItem := InvoiceItem MINUS (InvoiceItem WHERE InvNo = 12345);

even though he only asked the DBMS to do

    DELETE FROM InvoiceHeader WHERE InvNo = 12345;

This would then allow our users to be responsible for thier transactions. If they don't know what is being done in their name, why should they feel responsible at all?

Regards
Paul Vernon
Business Intelligence, IBM Global Services Received on Mon Nov 18 2002 - 19:58:47 CET