| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Greg Stark <gsstark(at)mit(dot)edu>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: ALTER TABLE ADD/DROP INHERITS |
| Date: | 2006-06-07 20:24:38 |
| Message-ID: | 871wu0ogs9.fsf@stark.xeocode.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > We should try very hard to avoid adding new reserved words, IMNSHO.
>
> *Especially* ones not sanctioned by the SQL spec. Reserving a word that
> is not listed as reserved in the standard is really a spec violation,
> because it means that spec-conforming SQL commands may fail.
I expected that but I haven't seen any agreement on a replacement syntax. The
only other one proposed was:
ALTER TABLE foo ALTER INHERITS ADD|DROP bar
and it received no comments. Should I just assume that's the direction to go
if nobody objects?
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-06-07 20:58:24 | Re: ALTER TABLE ADD/DROP INHERITS |
| Previous Message | Tom Lane | 2006-06-07 19:57:04 | Re: ALTER TABLE ADD/DROP INHERITS |