Re: Wrong string length from unicode database in Borland's app - Mailing list pgsql-general

From Tom Lane
Subject Re: Wrong string length from unicode database in Borland's app
Date
Msg-id 9235.1101063155@sss.pgh.pa.us
Whole thread Raw
In response to Wrong string length from unicode database in Borland's app  (Alex Guryanow <gav@nlr.ru>)
Responses Re: Wrong string length from unicode database in Borland's app
List pgsql-general
Alex Guryanow <gav@nlr.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

pgsql-general by date:

Previous
From: Dawid Kuroczko
Date:
Subject: COMMIT within function?
Next
From: "Net Virtual Mailing Lists"
Date:
Subject: Re: Join between databases or (???)