On Thu, 23 Sep 2004, Tom Lane wrote:
> Neil Conway <[EMAIL PROTECTED]> writes:
> > On Wed, 2004-09-22 at 23:00, Alvaro Herrera wrote:
> >> Could that include supporting SELECT INTO as well as both types of
> >> CREATE TABLE AS?
>
> > Right; my thinking is to have the parser construct SELECT INTO
Neil Conway <[EMAIL PROTECTED]> writes:
> On Wed, 2004-09-22 at 23:00, Alvaro Herrera wrote:
>> Could that include supporting SELECT INTO as well as both types of
>> CREATE TABLE AS?
> Right; my thinking is to have the parser construct SELECT INTO as a
> CreateTableAsStmt. That way all the code fo
On Wed, 2004-09-22 at 23:00, Alvaro Herrera wrote:
> Could that include supporting SELECT INTO as well as both types of
> CREATE TABLE AS?
Right; my thinking is to have the parser construct SELECT INTO as a
CreateTableAsStmt. That way all the code for creating the "into"
relation is centralized in
On Wed, Sep 22, 2004 at 06:48:12PM +1000, Neil Conway wrote:
> P.S. I'm beginning to think that rather than applying this patch as-is
> when we branch for 8.1, it might be a better idea to just bite the
> bullet and restructure CREATE TABLE AS as suggested above. Thoughts?
Could that include supp
This patch makes CREATE TABLE AS conform more closely to SQL:2003 by
adding support for the WITH [ NO ] DATA clause (per section 11.3). The
standard says that this clause is mandatory, but I think it should be
optional in PG (partly for backward compatibility, and partly because I
think that is san