Re: Unicode escapes with any backend encoding

From: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
To: Chapman Flack <chap(at)anastigmatix(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Unicode escapes with any backend encoding
Date: 2020-01-14 21:17:58
Message-ID: CAA8=A794h+boRZnOz+upJ6J6h=L8NbgMx+p2GMk6DZ9cdvbAYg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

cheers

andrew

--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-01-14 21:21:57 Re: planner support functions: handle GROUP BY estimates ?
Previous Message Tom Lane 2020-01-14 21:09:55 Re: proposal: type info support functions for functions that use "any" type