| From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
|---|---|
| To: | "Andrei Gaspar" <andi(at)softnrg(dot)dnttm(dot)ro>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: windows 1252 encoding |
| Date: | 2005-05-13 14:11:12 |
| Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE6C749E@algol.sollentuna.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> Is there a reason that the windows code page 1252 is not supported?
> The encoding Latin1 would be the most appropriate, but 1252
> is a superset of ISO8859-1 and supports more characters, and
> when I want to write them through odbc I get an error.
> psqlodbc 8 converts everything to utf-8 and then sends it to
> the server.
> I have a database with Latin1 encoding, the windows client
> code page is
> 1252 and for some characters I get
>
> could not convert UTF-8 character 0x00e2 to ISO8859-1
>
> A solution would be to use the UNICODE encoding in the
> database, but I have read that it's not safe on windows.
>
> So, any ideas?
This sounds like your client encoding is set to UTF-8. Try setting it to
LATIN1 as well (\encoding in psql).
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Eckermann | 2005-05-13 14:17:56 | Re: Delphi 2005, Postgresql, ZEOS & optimistic locking |
| Previous Message | Victor Spång Arthursson | 2005-05-13 13:21:51 | Re: How many rows if limit wasn't present? |