From: | Rod Taylor <rbt(at)rbt(dot)ca> |
---|---|
To: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: a quick question |
Date: | 2002-09-17 20:55:49 |
Message-ID: | 1032296150.32170.26.camel@jester |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 2002-09-17 at 16:44, scott.marlowe wrote:
> Hey, me and a few other folks were having a discussion off list, and the
> subject of inserts and missing columns came up. you may remember the point
> in the "I'm done" post by Bruce. It said:
>
> > o -Disallow missing columns in INSERT ... VALUES, per ANSI
> > > What is this, and why is it marked done?
>
> We used to allow INSERT INTO tab VALUES (...) to skip the trailing
> columns and automatically fill in null's. That is fixed, per ANSI.
>
> So, are we gonna make postgresql throw an error when someone tries to
> submit an insert with too few columns to match up to the implicit column
> list, or not?
There was a vote to keep previous behaviour when the column list wasn't
supplied, so it's not to ANSI spec, it's to our improved version ;)
INSERT INTO (...) VALUES (...) will not allow you to skip value entries,
but the keyword DEFAULT is available now, so it shouldn't be much of an
issue.
--
Rod Taylor
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2002-09-17 20:56:12 | Re: RPMS for 7.3 beta. |
Previous Message | scott.marlowe | 2002-09-17 20:44:54 | a quick question |