Re: [GENERAL] Wrong string length from unicode database in Borland's app

From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
To: "Alex Guryanow" <gav(at)nlr(dot)ru>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: [GENERAL] Wrong string length from unicode database in Borland's app
Date: 2004-11-23 20:55:56
Message-ID: 6EE64EF3AB31D5448D0007DD34EEB3412A7537@Herge.rcsinc.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

> 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

Alex, if you are using C++ builder and postgresql you should consider
using the Zeos database connection components for PostgreSQL. They are
lightweight, fast, and fairly well supported.

Merlin

Browse pgsql-odbc by date

  From Date Subject
Next Message Amir Zicherman 2004-11-24 06:52:34 autocommit off
Previous Message MB 2004-11-22 22:16:53 libodbc++ getCatalogs() problem