| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | Szymon Guz <mabewlun(at)gmail(dot)com>, 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:37:45 |
| Message-ID: | CAFj8pRCCbm4OReaYHeaF5B2FftHGDqTVEj-cschkGn+Wa6sFqQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2014-09-03 16:01 GMT+02:00 Kevin Grittner <kgrittn(at)ymail(dot)com>:
> 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.
>
>
It is true, but nobody reported bug yet, so who know, how this feature is
used.
Probably it needs a deeper analyze of difference between Pg CHAR(n) and
standard CHAR(n)
Pavel
> --
> Kevin Grittner
> EDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alanoly Andrews | 2014-09-03 15:13:56 | Cannot retrieve images inserted through VB and odbc, after a table reorganization. |
| Previous Message | Kevin Grittner | 2014-09-03 14:01:14 | Re: || operator |