Re: Charset conversion error - Mailing list pgsql-general

From Tatsuo Ishii
Subject Re: Charset conversion error
Date
Msg-id 20060530.152433.44793375.t-ishii@sraoss.co.jp
Whole thread Raw
In response to Re: Charset conversion error  ("Dan Black" <fireworker@gmail.com>)
Responses Re: Charset conversion error  ("Dan Black" <fireworker@gmail.com>)
List pgsql-general
> I think you are right. But everything was alright before I updated my
> database.

Previous version converted such characters to ASCII spaces. So
probably you have lots of bogus spaces anyway. If you think it's ok,
then you could your own CONVERSION which behaves similar to previous
version.
--
Tatsuo Ishii
SRA OSS, Inc. Japan

> So there are a lot of "incorrect" values in tables. And errors appear when I
> execute "SELECT * FROM table".
>
> 2006/5/30, Tatsuo Ishii <ishii@sraoss.co.jp>:
> >
> > > Hi, I have an error after updating my database up to 8.1.4 version.
> > > "SQL Error: ERROR:  character 0xb9 of encoding "WIN1251" has no
> > equivalent
> > > in "MULE_INTERNAL"'. "
> > > My client program encoding is windows-1251 and database encoding is
> > koi8.
> > > What can I do to rectify the situation?
> >
> > It suggests that Windows-1251's 0xb9 cannot be converted to KOI8. You
> > should check your Windows-1251 data.
> > --
> > Tatsuo Ishii
> > SRA OSS, Inc. Japan
> >
>
>
>
> --
> Verba volent, scripta manent
> Dan Black

pgsql-general by date:

Previous
From: kmi@st.uz
Date:
Subject: Re: Making query without trigger
Next
From: "Dan Black"
Date:
Subject: Re: Charset conversion error