Re: Unicode escapes with any backend encoding - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Unicode escapes with any backend encoding
Date
Msg-id 32278.1579037100@sss.pgh.pa.us
Whole thread Raw
In response to Re: Unicode escapes with any backend encoding  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: Unicode escapes with any backend encoding  (Chapman Flack <chap@anastigmatix.net>)
Re: Unicode escapes with any backend encoding  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
List 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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: planner support functions: handle GROUP BY estimates ?
Next
From: Peter Eisentraut
Date:
Subject: Re: Remove libpq.rc, use win32ver.rc for libpq