From: | Álvaro Hernández Tortosa <aht(at)8kdata(dot)com> |
---|---|
To: | Geoff Winkless <pgsqladmin(at)geoff(dot)dj> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Implementing full UTF-8 support (aka supporting 0x00) |
Date: | 2016-08-03 22:31:13 |
Message-ID: | 2b577088-91cc-87c4-bb8f-b77f574bbc2f@8kdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 03/08/16 21:42, Geoff Winkless wrote:
> On 3 August 2016 at 20:36, Álvaro Hernández Tortosa <aht(at)8kdata(dot)com> wrote:
>> Isn't the correct syntax something like:
>>
>> select E'\uc080', U&'\c080';
>>
>> ?
>>
>> It is a single character, 16 bit unicode sequence (see
>> https://www.postgresql.org/docs/current/static/sql-syntax-lexical.html).
> No, what you've done there is created the three-byte utf8 sequence \xec8280
>
> # select U&'\c080'::bytea;
> bytea
> ----------
> \xec8280
>
> It's not a UCS2 c080, it's utf8 c080.
>
> Geoff
Yes, you're absolutely right ^_^
Álvaro
--
Álvaro Hernández Tortosa
-----------
8Kdata
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2016-08-03 22:32:50 | Re: Small fix: avoid passing null pointers to memcpy() |
Previous Message | Tom Lane | 2016-08-03 22:06:45 | Re: Cache Hash Index meta page. |