Skip site navigation (1) Skip section navigation (2)

Re: TABLE command

From: "David Rowley" <dgrowley(at)gmail(dot)com>
To: "'Peter Eisentraut'" <peter_e(at)gmx(dot)net>
Cc: "'PG Hackers'" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: TABLE command
Date: 2008-10-30 23:04:42
Message-ID: EC8762ECB30D491182C23DAF43CD211B@amd64 (view raw or flat)
Thread:
Lists: pgsql-hackers
Peter Eisentraut Wrote:
> If I read this right, SQL would allow writing
> 
> TABLE foo;

Interesting; I managed to find it in the spec:

<Quote>
4) The <explicit table>
TABLE <table or query name>
is equivalent to the <table subquery>
( SELECT * FROM <table or query name> )
</Quote>

So going by that would the patch also have to support something like:

WITH a AS (SELECT * FROM b)
TABLE a; ?

I'd probably find it hard to find a use case. I'm too used to using SELECT *
FROM .. in psql. On the other hand last night I read a good web page
comparing the most popular RDBMS' for spec. compliance and PostgreSQL
probably was the most compliant all of the ones listed, (at least on the
topics covered). Oracle fails badly on '' IS NULL being true.

I enjoy seeing more spec compliant things being added. But on the other
hand, going with Tom's comments, if its lots of work for little gain... 




In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2008-10-30 23:14:49
Subject: Re: PG_PAGE_LAYOUT_VERSION 5 - time for change
Previous:From: Tom LaneDate: 2008-10-30 22:49:38
Subject: Re: User defined I/O conversion casts

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group