Re: [rfc] unicode escapes for extended strings - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: [rfc] unicode escapes for extended strings
Date
Msg-id 49E89713.EE98.0025.0@wicourts.gov
Whole thread Raw
In response to Re: [rfc] unicode escapes for extended strings  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: [rfc] unicode escapes for extended strings  (Marko Kreen <markokr@gmail.com>)
Re: [rfc] unicode escapes for extended strings  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> wrote:
> ISTM that one of the uses of this is to say "store the character
> that corresponds to this Unicode code point in whatever the database
> encoding is"
I would think you're right.  As long as the given character is in the
user's character set, we should allow it.  Presumably we've already
confirmed that they have an encoding scheme which allows them to store
everything in their character set.
-Kevin


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [rfc] unicode escapes for extended strings
Next
From: Marko Kreen
Date:
Subject: Re: [rfc] unicode escapes for extended strings