From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Rod Taylor <rbt(at)zort(dot)ca> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hackers List <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCHES] ANSI Compliant Inserts |
Date: | 2002-04-15 04:26:15 |
Message-ID: | Pine.LNX.4.30.0204150023520.717-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Rod Taylor writes:
> I submitted a patch which would make Postgresql ANSI compliant in
> regards to INSERT with a provided column list. As Tom states below,
> this is not full compliance.
>
> CREATE TABLE tab(col1 text, col2 text);
>
> INSERT INTO tab (col1, col2) VALUES ('val1'); -- bad by spec (enforced
> by patch)
> INSERT INTO tab (col1, col2) VALUES ('val1', 'val2'); -- good
>
> INSERT INTO tab VALUES ('val1'); -- bad by spec (not enforced)
> INSERT INTO tab VALUES ('val1', 'val2'); -- good
I recall that this was the behavior we agreed we wanted. IMHO, it would
be conditional on the INSERT ... VALUES (DEFAULT) capability being
provided. I'm not sure if that is there yet.
--
Peter Eisentraut peter_e(at)gmx(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-04-15 04:26:58 | Re: [PATCHES] ANSI Compliant Inserts |
Previous Message | Tom Lane | 2002-04-15 04:24:49 | Re: [PATCHES] ANSI Compliant Inserts |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-04-15 04:26:58 | Re: [PATCHES] ANSI Compliant Inserts |
Previous Message | Tom Lane | 2002-04-15 04:24:49 | Re: [PATCHES] ANSI Compliant Inserts |