From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Darren Duncan <darren(at)darrenduncan(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: DOMAINs and CASTs |
Date: | 2011-06-13 15:34:02 |
Message-ID: | 20110613153402.GA28357@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jun 13, 2011 at 03:39:39AM -0500, Jaime Casanova wrote:
> On Mon, Jun 6, 2011 at 6:36 AM, Peter Eisentraut <peter_e(at)gmx(dot)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(at)gmail(dot)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
Minor clarification attached.
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
Attachment | Content-Type | Size |
---|---|---|
casts_on_domains_02.patch | text/plain | 1.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2011-06-13 15:37:58 | Re: wrong message on REASSIGN OWNED |
Previous Message | Tom Lane | 2011-06-13 15:29:08 | Re: FOREIGN TABLE doc fix |