| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | Моисеев Алексей Николаевич <mp_man(at)ivc(dot)orw(dot)ru> |
| Cc: | "'pgadmin-support(at)postgresql(dot)org'" <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Re: Russian data in SQL_ASCII encoding |
| Date: | 2003-10-01 10:56:49 |
| Message-ID: | 3F7AB2F1.9080203@pse-consulting.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
Моисеев Алексей Николаевич wrote:
>Hi!!!
>Why russian data from tables in pgadmin 3 release in SQL_ASCII coding is not
>visible, but this data visible in pgadmin 2?
>What is the different between pgadmin3 and pgadmin2 for this problem?
>Thanks.
>
Hm,
I suspect that the server isn't able to translate your SQL_ASCII data to
Unicode to send it over the line. Currently, pgAdmin3 tells the backend
to send all data in Unicode, which should fit everything (if convertible).
Maybe we should leave the client connection SQL_ASCII if this is the
server encoding, because there are probably many SQL_ASCII encoded
databases around that actually contain non-ascii (thus non-convertible)
data.
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | b-vol | 2003-10-01 11:14:09 | Re: installation of pgAdmin3 on SuSE8.2 |
| Previous Message | Dave Page | 2003-10-01 09:47:19 | Re: Cannot create index if table name contains uppercase characters |