Re: Failure to coerce unknown type to specific type - Mailing list pgsql-bugs

From Robert Haas
Subject Re: Failure to coerce unknown type to specific type
Date
Msg-id CA+Tgmoav4gswNkA39SYdb3SdSBfrcHmU08=nXLNbxMZFg7UYsw@mail.gmail.com
Whole thread Raw
In response to Re: Failure to coerce unknown type to specific type  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Failure to coerce unknown type to specific type  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Wed, Apr 8, 2015 at 9:31 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Jeff Davis <pgsql@j-davis.com> writes:
>> Original report and patch by Karl Schnaitter.
>> create table a(u) as select '1';
>
> We should, in fact, fail that to begin with.  Unknown-type columns are
> a spectactularly horrid idea.

I agree.  So why don't we throw an error when someone tries to create one?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-bugs by date:

Previous
From: Jeff Janes
Date:
Subject: Re: BUG #13188: .pgpass does not work
Next
From: "bzb.dev001@gmail.com"
Date:
Subject: Re: BUG #13188: .pgpass does not work