Re: DOMAINs and CASTs
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: David Fetter <david@fetter.org>
Cc: Jaime Casanova <jaime@2ndquadrant.com>,
Peter Eisentraut <peter_e@gmx.net>, Robert Haas <robertmhaas@gmail.com>, Darren Duncan <darren@darrenduncan.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-11-29T02:46:07Z
Lists: pgsql-hackers
Attachments
- /rtmp/casts_on_domains_02.patch (text/x-diff) patch
David Fetter wrote: > 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@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 > > Minor clarification attached. What happened to this patch for casts on domains from June? -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +