Re: Failure to coerce unknown type to specific type

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, Postgres-Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Failure to coerce unknown type to specific type
Date: 2015-04-29 21:50:15
Message-ID: CA+Tgmoav4gswNkA39SYdb3SdSBfrcHmU08=nXLNbxMZFg7UYsw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Wed, Apr 8, 2015 at 9:31 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Jeff Davis <pgsql(at)j-davis(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2015-04-29 22:37:51 Re: Failure to coerce unknown type to specific type
Previous Message bzb.dev001@gmail.com 2015-04-29 21:39:30 Re: BUG #13188: .pgpass does not work

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-04-29 21:54:01 Re: alternative compression algorithms?
Previous Message David Steele 2015-04-29 21:31:25 Re: Proposal: knowing detail of config files via SQL