| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Szymon Guz <mabewlun(at)gmail(dot)com> |
| Cc: | Vinayak <vinpokale(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: || operator |
| Date: | 2014-09-03 14:01:14 |
| Message-ID: | 1409752874.83247.YahooMailNeo@web122305.mail.ne1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> 2014-09-03 15:25 GMT+02:00 Szymon Guz <mabewlun(at)gmail(dot)com>:
>> I think we should have this in core, as this definitely is a bug.
>
> hard to say - anything about CHAR(N) is strange,
On a quick scan of the standard, it looks like our current behavior
is non-conforming.
> and this change can break existing applications :(
That is true, but since the only point of supporting CHAR(n) is to
satisfy requirements of the standard, it might be something we
should do, if technically feasible.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2014-09-03 14:37:45 | Re: || operator |
| Previous Message | Adrian Klaver | 2014-09-03 13:57:07 | Re: || operator |