Gavin Sherry wrote:
Slony can utilise this by setting the client encoding to the encoding of the server it is working on. The problem should go away then.
IMHO slony should behave as a unicode application, i.e. use UTF8 client encoding for all database connections. This will have pgsql apply conversions transparently, because most server encodings can convert happily from and to UTF8. The exception is SQL_ASCII and MULE_INTERNAL, in these cases client encoding must match server encoding, hoping that data will be stored correctly.
pgAdmin runs correctly with this scheme. Regards, Andreas _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
