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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Joseph Adams <joeyadams3(dot)14159(at)gmail(dot)com>, 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:23:14
Message-ID: 4BE31722.4080301@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Joseph Adams <joeyadams3(dot)14159(at)gmail(dot)com> writes:
>
>> This isn't exactly a bug, but it could be considered unintuitive
>> behavior.
>>
>
> It's required by the SQL standard.
>
>
>

And many places regard "select *" in anything other than throw-away
queries as bad practice anyway. I have seen people get bitten by it over
and over again, and I have worked at companies where it is explicitly
forbidden in coding standards.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andy Lester 2010-05-06 19:29:55 PATCH: Minor notes in CLUSTER page
Previous Message Merlin Moncure 2010-05-06 19:10:22 Re: SELECT * in a CREATE VIEW statement doesn't update column set automatically