![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
When pg-server is version 7.1.3 windows app works fine, but when pg-server is version 7.4.6 or 8.0beta4 under certain conditions the app receives strings with wrong lengths. |
|
But by executing the query select volume, trim(number) from issue where mag_id = 25403; the datagrid component (that displays query's results) contains in second column values with length of 32769. |
#2
| |||
| |||
|
|
When pg-server is version 7.1.3 windows app works fine, but when pg-server is version 7.4.6 or 8.0beta4 under certain conditions the app receives strings with wrong lengths. TL> If you try the same query in plain psql, what do you get? I get all ok. |
#3
| |||
| |||
|
|
TL> Alex Guryanow <gav (AT) nlr (DOT) ru> writes: When pg-server is version 7.1.3 windows app works fine, but when pg-server is version 7.4.6 or 8.0beta4 under certain conditions the app receives strings with wrong lengths. TL> Are both servers set up with the same database encoding? I think the answer is yes. For both servers the command "initdb" was executed only with parameter DATADIR. At the same time the locale is set up to "ru_RU.cp1251". But by creating the database I specify parameter "-E UNICODE" and "psql -l" shows that the database is in UNICODE encoding. One time I have forgotten to specify '-E UNICODE' by executing createdb and windows app worked fine with 7.4.6 |
![]() |
| Thread Tools | |
| Display Modes | |
| |