Re: DOMAINs and CASTs
| От | Jaime Casanova |
|---|---|
| Тема | Re: DOMAINs and CASTs |
| Дата | |
| Msg-id | BANLkTim5c7Z+6ZfO2VpbTmaytLzTvPiVNg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: DOMAINs and CASTs (Peter Eisentraut <peter_e@gmx.net>) |
| Ответы |
Re: DOMAINs and CASTs
Re: DOMAINs and CASTs |
| Список | pgsql-hackers |
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
Вложения
В списке pgsql-hackers по дате отправления: