From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jan Wieck <JanWieck(at)yahoo(dot)com>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: "ALSO" keyword to "CREATE RULE" patch |
Date: | 2004-03-04 15:36:22 |
Message-ID: | 200403041536.i24FaMG06712@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-patches |
Fabien COELHO wrote:
>
> > I thought the syntax came from Berkeley. We can add ALSO if folks like
> > it. I can't think of cases where we have keywords for both on and off
> > behavior, and allow a default if the keyword is missing.
>
> ALTER TABLE ... DROP CONSTRAINT ... [ RESTRICT | CASCADE ] ;
>
> CREATE TABLE ... [ WITH OIDS | WITHOUT OIDS ] ... ;
>
> CREATE USER ... [ CREATEDB | NOCREATEDB ] ... ;
>
> IMHO, from the language design point of view, it seems better if all
> options have a name.
Makes sense to me now. No one liked the non-INSTEAD rule description,
for sure.
Shoot me the patch again and I will put in the the queue. Thanks.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2004-03-04 15:52:24 | Re: "ALSO" keyword to "CREATE RULE" patch |
Previous Message | Fabien COELHO | 2004-03-04 15:13:19 | Re: "ALSO" keyword to "CREATE RULE" patch |
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2004-03-04 15:52:24 | Re: "ALSO" keyword to "CREATE RULE" patch |
Previous Message | Fabien COELHO | 2004-03-04 15:13:19 | Re: "ALSO" keyword to "CREATE RULE" patch |