Re: Unicode escapes with any backend encoding
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: Chapman Flack <chap@anastigmatix.net>,
PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2020-01-14T21:25:00Z
Lists: pgsql-hackers
Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes: > On Wed, Jan 15, 2020 at 4:25 AM Chapman Flack <chap@anastigmatix.net> wrote: >> On 1/14/20 10:10 AM, Tom Lane wrote: >>> to me that this error is just useless pedantry. As long as the DB >>> encoding can represent the desired character, it should be transparent >>> to users. >> That's my position too. > and mine. I'm confused --- yesterday you seemed to be against this idea. Have you changed your mind? I'll gladly go change the patch if people are on board with this. regards, tom lane
Commits
-
Allow Unicode escapes in any server encoding, not only UTF-8.
- a6525588b7c2 13.0 landed