On 10 Jan 2011, at 16:32, J. Hondius wrote: > Hi all, > > We have a product with a PostgreSQLdatabase (unicode) > It has a (legacy) client app that uses client_encoding = win1521 > The legacy app will be around for several years. > It cannot change to unicode. > > There also is a new client app, written in java. > It uses client_encoding = unicode. I think you may be able to set the client encoding at the user level. In that case you could use a different user for the legacy app than you use for the java app and have the appropriate client encoding for both cases. try: ALTER ROLE foo SET client_encoding TO 'win1251'; Note: This is just off the top of my head, I haven't actually verified any of this. Alban Hertroys -- If you can't see the forest for the trees, cut the trees and you'll see there is no forest. !DSPAM:737,4d2c9b0a11871070112136! -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
