| From: | "Hiroshi Saito" <saito(at)inetrt(dot)skcapi(dot)co(dot)jp> |
|---|---|
| To: | "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de> |
| Cc: | "Serguei A(dot) Mokhov" <mokhov(at)cs(dot)concordia(dot)ca>, Ângelo Marcos Rigo <angelo_rigo(at)yahoo(dot)com(dot)br>, <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: |
| Date: | 2003-10-01 17:39:24 |
| Message-ID: | 021401c38842$f46fc2d0$1f324d80@w2k |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
From: "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>
(snip)
> >>This is correctly diagnosed, non-ascii data in a SQL_ASCII encoded
> >>database will not be shown because the server doesn't know how to encode
> >>it in Unicode.
> >>
> >>This is fixed for HEAD and BRANCH.
> >
> >No.
> >Server encoding as below.
> >
>
> This is not suitable for non-ascii chars, because the upper bit will be
> chopped off (ascii->utf8), effectively destroying the string, or
> converted to a bogus char (xx), effectively destroying the string.
Hmm..
Is it a specific code or all code?
However,
Will you absorb all the bugs of PostgreSQL?
regards,
Hiroshi Saito
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Pflug | 2003-10-01 18:05:45 | Re: |
| Previous Message | Andreas Pflug | 2003-10-01 17:33:32 | Re: |