[Mono-list] Special-Signs Problem

Francisco Figueiredo Jr. fxjrlists at yahoo.com.br
Thu Jan 19 12:07:15 EST 2006

--- Helge Lenuweit <helge at lenuweit.net> escreveu:

> Hello Jan,
> it should help to provide the appropriate client-side encoding in the 
> connection string, like so: encoding=LATIN1;. For .NET, I found it 
> easiest to switch to encoding=UNICODE generally as .NET string data are 
> unicode characters anyway.
> Regards,
> Helge

Hi Helge, Jan.

Npgsql only supports two encodings: ASCII (default) and UNICODE. If your
database is in any other encoding, like LATIN1, you should use encoding=UNICODE
in your connection string. Postgresql server will do the conversion
automagically for you.

I'm thinking about changing the default to UNICODE in order to avoid this
problem. We receive sometimes reports of problems like that. Sorry Jan. And
thanks Helge for providing the correct answer for this.


Francisco Figueiredo Jr.


Yahoo! doce lar. Faça do Yahoo! sua homepage. 

More information about the Mono-list mailing list