From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | mp_man(at)ivc(dot)orw(dot)ru |
Cc: | "[pgADMIN]" <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Russian data in SQL_ASCII encoding |
Date: | 2003-10-01 15:31:59 |
Message-ID: | 3F7AF36F.1080206@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Andreas Pflug wrote:
> Моисеев Алексей Николаевич 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.
I updated pgConn.cpp and pgConn.h to be SQL_ASCII aware. There's some
heavy work in cvs underway. If you have a pgAdmin3 source installation
to test it, you should get these two files only.
Regards,
Andreas
>
>
> Regards,
> Andreas
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Network Administrator | 2003-10-01 15:35:23 | Re: Sorting questions and an SSL question |
Previous Message | Andreas Pflug | 2003-10-01 15:25:55 | Re: Sorting questions and an SSL question |