On Fri, Mar 25, 2011 at 03:33, Kasia Tuszynska <ktuszynska(at)esri(dot)com> wrote:
> We have a customer in Japan who would be interested in this fix, in the future. Would you like me to enter it as an official Postgres bug?
Not a bug at all -- there are at least 3 versions of "EUCJP" encodings, and
postgres just supports one of them. I think it won't be changed in the near
term. So, you would need to define a CONVERSION for your purpose as of now.
However, I think we could have an extension of conversion procedure set
for Japanese confused encodings out of the core.
In response to
pgsql-bugs by date
|Next:||From: Tatsuo Ishii||Date: 2011-03-25 02:24:10|
|Subject: Re: ERROR: character 0xe3809c of encoding "UTF8" has no
equivalent in EUC_JP|
|Previous:||From: Kris Jurka||Date: 2011-03-24 20:32:27|
|Subject: Re: BUG #5943: jdbc client doesn't omit pg_toast_temp tables
from schema views|