| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Grzegorz Szpetkowski <gszpetkowski(at)gmail(dot)com>, pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: ALTER TABLE doc small thing |
| Date: | 2011-09-10 13:24:50 |
| Message-ID: | 201109101324.p8ADOpr29212@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Robert Haas wrote:
> On Mon, May 9, 2011 at 2:12 PM, Grzegorz Szpetkowski
> <gszpetkowski(at)gmail(dot)com> wrote:
> > "NOTE 30 ? If MATCH FULL or MATCH PARTIAL is specified for a
> > referential constraint and if the referencing table has only one
> > column specified in <referential constraint definition> for that
> > referential constraint, or if the referencing table has more than one
> > specified column for that <referential constraint definition>, but
> > none of those columns is nullable, then the effect is the same as if
> > no
> > <match type> were specified."
> >
> > I found that in SQL:2003 draft, so in above case MATCH FULL is
> > syntactically ok, but rather confusing and effectively do nothing
> > (maybe just impression purpose).
>
> I guess we could remove it, but I don't think it's really doing any harm.
I find the MATCH FULL makes the example less real-world accurate, so I
removed the specification from the example.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2011-09-10 13:32:14 | Re: 7.1. Overview (The SQL Language) |
| Previous Message | Bruce Momjian | 2011-09-09 23:48:22 | Re: createuser/dropuser username |