Am 15.11.2013 06:13, schrieb Ashesh Vashi: > Sure - I will look into it..
Thanks for looking into it. One more thing that I forgot to mention: The problem only appears if the database encoding is not already UNICODE, but, for instance, LATIN1 or WIN1252. This is unfortunately still a quite frequent setting here in Europe. So you need to create such a database to reproduce. If your template1 database is already UTF8, you need to create it from template0.
-- Christoph -- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers
