Re: cascade and restrict options to alter domain drop constraint

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Marc Munro <marc(at)bloodnok(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: cascade and restrict options to alter domain drop constraint
Date: 2007-09-25 21:23:58
Message-ID: 28201.1190755438@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Marc Munro <marc(at)bloodnok(dot)com> writes:
> I am puzzled by the cascade and restrict options to the alter domain
> drop constraint command.

They don't do anything.

I think they were put in because we have this meme that the SQL spec
requires RESTRICT/CASCADE options on every type of DROP, but so far
as I can see, SQL99 has no such option for ALTER DOMAIN DROP CONSTRAINT.
So maybe it's a bug that we take the options for it. Or maybe it's
better to leave them there, in case people are expecting them to
be there on the same reasoning.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2007-09-25 21:34:04 Re: Can't connect (2 dbs) or login (2 others)
Previous Message Madison Kelly 2007-09-25 20:28:47 Re: Manually clearing "database "foo" is being accessed by other users"