| From: | Andrei Gaspar <andi(at)softnrg(dot)dnttm(dot)ro> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | windows 1252 encoding |
| Date: | 2005-05-13 12:46:20 |
| Message-ID: | 4284A19C.6040508@softnrg.dnttm.ro |
| 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?
Andrei
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.11.9 - Release Date: 5/12/2005
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Schuchardt | 2005-05-13 13:11:00 | Re: Delphi 2005, Postgresql, ZEOS & optimistic locking |
| Previous Message | Richard Huxton | 2005-05-13 12:45:03 | Re: How many rows if limit wasn't present? |