| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
| Cc: | 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-06 11:36:30 |
| Message-ID: | 1307360190.20678.4.camel@fsopti579.F-Secure.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
It's debatable whether it's an implementation restriction anyway. If
you want to create casts from or to a domain, maybe distinct types or
type aliases or something like that would be a more appropriate feature
in the long run.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-06-06 11:59:58 | Re: reducing the overhead of frequent table locks - now, with WIP patch |
| Previous Message | Heikki Linnakangas | 2011-06-06 10:51:45 | Re: WIP: Fast GiST index build |