Re: Unicode escapes with any backend encoding
От | Andrew Dunstan |
---|---|
Тема | Re: Unicode escapes with any backend encoding |
Дата | |
Msg-id | CAA8=A781rCyH+iOwmOvsjpLc9B6FuWa8v-LnCUdtc0Y8KfTqHQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Unicode escapes with any backend encoding (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Unicode escapes with any backend encoding
|
Список | pgsql-hackers |
On Tue, Jan 14, 2020 at 10:02 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > > > Grepping for other direct uses of unicode_to_utf8(), I notice that > there are a couple of places in the JSON code where we have a similar > restriction that you can only write a Unicode escape in UTF8 server > encoding. I'm not sure whether these same semantics could be > applied there, so I didn't touch that. > Off the cuff I'd be inclined to say we should keep the text escape rules the same. We've already extended the JSON standard y allowing non-UTF8 encodings. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: