| From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | arul(at)fast(dot)au(dot)fujitsu(dot)com, PostgreSQL-Dev <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal - Support for National Characters functionality |
| Date: | 2013-07-05 05:40:44 |
| Message-ID: | CAGTBQpY=dOM=Z7-8jvNiw6hdgFBry3wf4-H7ABiG2Uwy4Zkz3g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 5, 2013 at 2:02 AM, Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
>> - Support for NATIONAL_CHARACTER_SET GUC variable that will determine
>> the encoding that will be used in NCHAR/NVARCHAR columns.
>
> You said NCHAR's encoding is UTF-8. Why do you need the GUC if NCHAR's
> encoding is fixed to UTF-8?
Not only that, but I don't think it can be a GUC. Maybe a compile-time
switch, but if it were a GUC, how do you handle an existing database
in UTF-8 when the setting is switched to UTF-16? Re-encode everything?
Store the encoding along each value? It's a mess.
Either fix it at UTF-8, or make it a compile-time thing, I'd say.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2013-07-05 06:02:25 | Re: WITH CHECK OPTION for auto-updatable views |
| Previous Message | Amit Kapila | 2013-07-05 05:19:17 | Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |