On May 9, 2006 01:03 pm, jef peeraer <jef.peeraer@xxxxxxxxxx> wrote: > well i recently struggled with the same problem. After a lot of trial > and error and reading, it seems that an ascii encoded database can't use > its client encoding capabilities ( set client_encoding to utf8 ). > i think the easist solution is to do a dump, recreate the database with > a proper encoding, and restore the dump. You also need to convert any non-ASCII encoded characters present in the dump to UTF-8, prior to restoring it. If you're lucky, and they're all the same (ie. LATIN1 or something), you can use iconv to easily do that. Remember to change the set client_encoding line in the dump file, too. -- Alan
