Re: DOMAINs and CASTs

Jaime Casanova <jaime@2ndquadrant.com>

From: Jaime Casanova <jaime@2ndquadrant.com>

To: Peter Eisentraut <peter_e@gmx.net>

Cc: Robert Haas <robertmhaas@gmail.com>, Darren Duncan <darren@darrenduncan.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2011-06-13T08:39:39Z

Lists: pgsql-hackers

Attachments

casts_on_domains.patch (text/x-patch) patch

On Mon, Jun 6, 2011 at 6:36 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
> On tis, 2011-05-17 at 14:11 -0500, Jaime Casanova wrote:
>> On Tue, May 17, 2011 at 12:19 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>> >
>> > The more controversial question is what to do if someone tries to
>> > create such a cast anyway.  We could just ignore that as we do now, or
>> > we could throw a NOTICE, WARNING, or ERROR.
>>
>> IMHO, not being an error per se but an implementation limitation i
>> would prefer to send a WARNING
>
> Implementation limitations are normally reported as errors.  I don't see
> why it should be different here.
>

ok, patch reports an error... do we want to backpatch this? if we want
to do so maybe we can backpatch as a warning

-- 
Jaime Casanova         www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación