On Tue, Jan 11, 2011 at 3:23 AM, J. Hondius wrote:
> -Should i filter out all non win1252 charachters at the new java app and
> substitute them? (not so nice, i'd like to have the chars in the db)
>
If one of your client's cannot handle the data stored in the DB, then
you should not store that da
Hi,
Please advise.
We have a product with a PostgreSQLdatabase (UTF-8, PG 8.0 and 8.3)
It has a (legacy) client app that uses client_encoding = win1521 on the
connection since it uses win1252 internally.
The legacy app will be around for several years.
It cannot change to unicode.
There is a