Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Tue, 25 Sep 2007 17:23:58 -0400
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
- References:
- cascade and restrict options to alter domain drop constraint
- From: Marc Munro
- cascade and restrict options to alter domain drop constraint
- Prev by Date: Re: Manually clearing "database "foo" is being accessed by other users"
- Next by Date: pg_restore - invalid file problem
- Previous by thread: cascade and restrict options to alter domain drop constraint
- Next by thread: pg_restore - invalid file problem
- Indexes: