Philip Warner wrote:
> At 11:33 1/07/00 +0200, Jan Wieck wrote:
> >
> >Was late for me too, and maybe the answer was too lazy. So
> >let me give you an example of what I meant:
> >
>
> About 5 mins after I hit the send button on my last message I realized the
> error in my ways (again).
At 11:33 1/07/00 +0200, Jan Wieck wrote:
>
>Was late for me too, and maybe the answer was too lazy. So
>let me give you an example of what I meant:
>
About 5 mins after I hit the send button on my last message I realized the
error in my ways (again). There are probably limitations one
Philip Warner wrote:
> At 17:56 30/06/00 +0200, Jan Wieck wrote:
> >
> >For gods sake they don't have. And I'm uncertain that it
> >should ever work.
>
> Sorry...I'm the one to blame for the suggestion. My only defense is it was
> late, and I was misled by the parser...never the less.
> >How should a RESTRICT or ON
> >DELETE CASCADE work in that scenario?
>
> Perhaps as Check constraints on all tables in the view...for the most part
> I would not expect complex views to be used in this way, but since this is
> what the user would have to do anyway, why not do it for t
At 17:56 30/06/00 +0200, Jan Wieck wrote:
>
>For gods sake they don't have. And I'm uncertain that it
>should ever work.
Sorry...I'm the one to blame for the suggestion. My only defense is it was
late, and I was misled by the parser...never the less...
>How should a RESTRICT o
