Re: insert statements

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Vince Vielhaber <vev(at)michvhf(dot)com>
Cc: Rod Taylor <rbt(at)zort(dot)ca>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: insert statements
Date: 2002-03-14 17:39:55
Message-ID: 16487.1016127595@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Vince Vielhaber <vev(at)michvhf(dot)com> writes:
>> What's your definition of "other dbs"? The above statement is quite
>> clearly in violation of the SQL92 and SQL99 specifications:

> And nowhere does it say that <column name> cannot be qualified with
> the table name in front of it.

Au contraire, that is EXACTLY what that bit of BNF is saying. If
they'd meant to allow this construction then the BNF would refer to
<qualified name>, not just <identifier>.

> Looking at the entire message noted
> above the list of other dbs that support it is now Oracle, Sybase,
> MS-SQL and mysql. If "other dbs" ends up the equivilent of "everything
> but PostgreSQL" then which one is non-standard?

Out of curiosity, what do these guys do if I try the obvious

insert into foo (bar.col) ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2002-03-14 17:40:36 Re: 'Following' the Primary key
Previous Message Tom Lane 2002-03-14 17:27:23 Re: Bug #613: Sequence values fall back to previously chec