Well the server does have the capability to convert from the server encoding to the client encoding and the other way around. To get this working you need a server encoding which can be convertet to the clientencoding. UNICODE (UTF8) is a good starting point here. Now the server needs to know waht the encoding of the client is. You can set the client encoding from the client by sending "set client_encoding to <whatever it is>" to the server after the connection is started. There are other ways which can solve other problems (see character set support in the manual), for my application this way wroked best and makes it simple to work with different clientencodings. Best regards Ivo Am Dienstag, 25. Juli 2006 12.27 schrieb adey: > I had the same problem when upgrading v7.4 database to v8, SQL-ASCII to > UTF8 - we had to replace single backslashes with double backslashes in the > v7 database to get the data to display correctly, then dump and restore in > v8 / UTF8. Have we done something wrong please? > > On 7/22/06, Peter Eisentraut <peter_e@xxxxxxx> wrote: > > PostgreSQL Admin wrote: > > > I had my database set to SQL_ASCII and switched to UTF8, but now I > > > notice that I must add a slash for periods/dots ( \. vs . ) to insert > > > into varchar. Is this normal? > > > > No. > > > > -- > > Peter Eisentraut > > http://developer.postgresql.org/~petere/ > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 4: Have you searched our list archives? > > > > http://archives.postgresql.org
