| From: | Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | Johann Zuschlag <zuschlag2(at)online(dot)de> |
| Cc: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: Unicode is not UTF-8. was :psqlODBC-Driver Test / text |
| Date: | 2006-04-01 01:35:37 |
| Message-ID: | 442DD8E9.2080007@tpf.co.jp |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
Johann Zuschlag wrote:
> Johann Zuschlag schrieb:
>
>>
> No, again wrong. Or is it more like this:
>
> 1.
> a) locale = ISO8859-1
> backend-1 = LATIN1
>
> b) locale = UTF-8
> backend-2 = Unicode
What do you mean by the Unicode and are you really setting b)
as above ?
First note that in PostgreSQL the encoding has nothing to do
with the locale setting. Though PostgreSQL manages the encoding
settings by itself, as for the locale setting it completely relies
on the OS environment. There exists an essential flaw from the first.
Anyway you can change the encoding as you like per database at
createdb time but the locale setting LC_COLLATE and LC_CTYPE are
fixed at initdb time.
regards,
Hiroshi Inoue
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2006-04-01 06:00:28 | Re: Strange Update query ... |
| Previous Message | Bart Samwel | 2006-04-01 01:26:58 | Re: Unicode is not UTF-8. was :psqlODBC-Driver Test / text |