From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Thomas H(dot)" <me(at)alternize(dot)com>, "Jaime Casanova" <systemguards(at)gmail(dot)com>, <pgsql-bugs(at)postgresql(dot)org>,"mike" <mike(at)thegodshalls(dot)com> |
Subject: | Re: No error when FROM is missing in subquery |
Date: | 2006-12-19 15:37:43 |
Message-ID: | 4587B2E6.EE98.0025.0@wicourts.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
>>> On Tue, Dec 19, 2006 at 9:23 AM, in message
<24047(dot)1166541794(at)sss(dot)pgh(dot)pa(dot)us>,
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
>> It's easy to see how it resolves the column references; but the
syntax
>> is still not compliant with the SQL standard. The FROM clause is
>> required. We could call it a PostgreSQL extension, but I'm curious
if
>> anyone actually finds it useful.
>
> You've never done "SELECT some_expression" ?
Not, as far as I can recall, in the ANSI SQL spec. Did I miss
something?
I'm having trouble seeing how it is a useful construct in the context
of a scalar subquery. A non-standard extension should be useful in some
way.
-Kevin
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-12-19 15:58:48 | Re: No error when FROM is missing in subquery |
Previous Message | Tom Lane | 2006-12-19 15:23:14 | Re: No error when FROM is missing in subquery |