| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
| Cc: | Chapman Flack <chap(at)anastigmatix(dot)net>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Unicode escapes with any backend encoding |
| Date: | 2020-01-14 21:25:00 |
| Message-ID: | 32278.1579037100@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
> On Wed, Jan 15, 2020 at 4:25 AM Chapman Flack <chap(at)anastigmatix(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2020-01-14 21:34:10 | Re: Remove libpq.rc, use win32ver.rc for libpq |
| Previous Message | Tom Lane | 2020-01-14 21:21:57 | Re: planner support functions: handle GROUP BY estimates ? |