Search Postgresql Archives

Re: windows 1252 encoding

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> 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

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

               http://archives.postgresql.org


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux