Re: SELECT * in a CREATE VIEW statement doesn't update column set automatically

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Joseph Adams <joeyadams3(dot)14159(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SELECT * in a CREATE VIEW statement doesn't update column set automatically
Date: 2010-05-06 19:10:22
Message-ID: m2vb42b73151005061210g845b7ea4t85481ebac7219a2@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 6, 2010 at 3:01 PM, Joseph Adams <joeyadams3(dot)14159(at)gmail(dot)com> wrote:
> This isn't exactly a bug, but it could be considered unintuitive
> behavior.  Consider this:

by unintuitive you mean: 'explicitly defined in the SQL standard' :-).
I happen to agree with you but that's irrelevant. If you absolutely
require this use the composite type workaround.

merlin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2010-05-06 19:23:14 Re: SELECT * in a CREATE VIEW statement doesn't update column set automatically
Previous Message Tom Lane 2010-05-06 19:09:28 Re: SELECT * in a CREATE VIEW statement doesn't update column set automatically