Re: psqlOdbc Ansi + BDE issues

From: "Miguel Juan" <mjuan(at)cibal(dot)es>
To: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: psqlOdbc Ansi + BDE issues
Date: 2005-11-15 15:07:53
Message-ID: 003901c5e9f6$5a427aa0$07c8a8c0@Miguel
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Hello,
----- Original Message -----
From: Dave Page
To: Miguel Juan ; pgsql-odbc(at)postgresql(dot)org
Sent: Tuesday, November 15, 2005 11:08 AM
Subject: Re: [ODBC] psqlOdbc Ansi + BDE issues

----------------------------------------------------------------------------
From: pgsql-odbc-owner(at)postgresql(dot)org [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Miguel Juan
Sent: 11 November 2005 12:56
To: pgsql-odbc(at)postgresql(dot)org
Subject: [ODBC] psqlOdbc Ansi + BDE issues

Hi,

I'm testing the Ansi version of the psqlodbc-08.01.0100 and I have found a few isues.

If you open a table with the BDE SQL explorer, now it shows all the text fields (char, varchar and text), but for the TEXT type it show the contents as MEMO. This behavior could be changed in prior versions unchecking the "Text as LongVarChar" option and checking the "Longest" option in the "Unknown Sizes" section.

Now, it can be fixed only changing the "Max LongVarchar" edit to 254. It looks like the driver it is not using the "longest" option in the configuration.

No - longest doesn't work anymore because there is no sensible way to figure it out with the libpq driver architecture. It was only ever there to support pre-6.4 servers that couldn't report the defined column width (see the config.htm doc for details).

That aside, shouldn't TEXT equate to MEMO anyway?

Sure yes, but before (version 7.x) TEXT equate to VARCHAR if the longest size is under 255 characters, and this change the behavior of some Delphi components, such as TDataGrid, etc. Anyway, it could be solved easily with a few lines of code.
If you open the database schema with the sql explorer it does not show all the tables, and each table that it shows appears 6 times. It is easy to reproduce, because it happens with all the system tables.

Please try 08.01.0101.
Now it shows each system table about four times, and each user table about three times. Still not showing all the tables in the database.

Regards, Dave.

Regards,

Miguel Juan

In response to

Browse pgsql-odbc by date

  From Date Subject
Next Message john m langdon 2005-11-15 16:58:18 PgSQL ODBC, ADO and output parameters
Previous Message Tobias Britz 2005-11-15 15:07:18 Visual Studio 2005 not happy with postgresql