From: | Marko Kreen <markokr(at)gmail(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org, Sam Mason <sam(at)samason(dot)me(dot)uk> |
Subject: | Re: [rfc] unicode escapes for extended strings |
Date: | 2009-04-17 20:16:44 |
Message-ID: | e51f66da0904171316q3ccea150ha511e2dce2db5040@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 4/17/09, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)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.
It is probably good idea, but currently I just followed what the U&
strings do.
I can change my patch to do it, but it is probably more urgent in U&
case to decide whether they should work in other encodings too.
--
marko
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2009-04-17 20:42:31 | Re: psql with "Function Type" in \df |
Previous Message | Kevin Grittner | 2009-04-17 19:49:55 | Re: [rfc] unicode escapes for extended strings |