Tom Lane wrote:
> Is the database's locale set to something that works with EUC_JP? You
> can't just whack the encoding around without paying attention to having
> a compatible locale setting ... and unfortunately, PG doesn't have
> enough knowledge about locales to warn you when you choose a comb
Jon Keating wrote:
I have a database with the default encoding set to EUC_JP and the client
(using pgAdmin III) is set to EUC_JP as well.
pgAdmin uses Unicode (unless the DB is SQL_ASCII or MULE_INTERNAL), you
won't get happy if you change it using a SET command.
Regards,
Andreas
"Jon Keating" <[EMAIL PROTECTED]> writes:
> I have a database with the default encoding set to EUC_JP and the client
> (using pgAdmin III) is set to EUC_JP as well.
Is the database's locale set to something that works with EUC_JP? You
can't just whack the encoding around without paying attention
