From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alex Guryanow <gav(at)nlr(dot)ru> |
Cc: | pgsq-odbc(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Wrong string length from unicode database in Borland's app |
Date: | 2004-11-21 18:52:35 |
Message-ID: | 9235.1101063155@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-odbc |
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.
Are both servers set up with the same database encoding? (Is the 7.1
server even compiled to support non-ASCII encodings?)
> 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.
If you try the same query in plain psql, what do you get? What is in
the wrong-length value, exactly?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Net Virtual Mailing Lists | 2004-11-21 21:06:17 | Re: Join between databases or (???) |
Previous Message | Dawid Kuroczko | 2004-11-21 18:29:26 | COMMIT within function? |
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Guryanow | 2004-11-22 08:11:26 | Re: Wrong string length from unicode database in Borland's app |
Previous Message | Alex Guryanow | 2004-11-21 15:04:59 | Wrong string length from unicode database in Borland's app |