Thread: New libpq driver snapshot
I've uploaded an update of the new libpq driver to ftp://ftp.postgresql.org/pub/odbc/versions/snapshots/. It will appear on the PostgreSQL website and ftp mirrors within a day or so. This version fixes all known memory leaks and other issues found in the first snapshot of the new libpq driver, except the threading issue I've found when using transactions in ODBCBench. *** It is essential that this version gets lots of testing in order to ensure it is of production quality before we make a proper release, so please take the time to test your applications with it! *** To aid testing, this driver will install as PostgreSQL-libpq, and may be installed in parallel with non-libpq versions of the driver. Regards, Dave.
> -----Original Message----- > From: Miguel Juan [mailto:mjuan@cibal.es] > Sent: 22 July 2005 11:26 > To: Dave Page; pgsql-odbc@postgresql.org > Subject: Re: [ODBC] New libpq driver snapshot > > Hello, > > I just tried the latest snapshot under BDE (Borland Database Engine) > environment and the driver still have the same problems with de > text/char/varchar fields. > > With version 8 not libpq the fields appear in blank, but now > it do not show > field at all. Some time ago I done some Log comparation and I > found out that > the return type of the fields where somekind diferent between > version 7 and > version 8. > > Do you want any information, Logs or anything? > > Note: I am not a Visual C programmer, but I can try do do > some debug if you > need it. Can you write a program to, as simply as possible, open a connection, execute "select vesion();" and retrieve the result using BDE? Does that work? If not, can you post mylog output? Feel free to try to debug it your self as well... Regards Dave.
Hello,
I just tried the latest snapshot under BDE (Borland Database Engine)
environment and the driver still have the same problems with de
text/char/varchar fields.
With version 8 not libpq the fields appear in blank, but now it do not show
field at all. Some time ago I done some Log comparation and I found out that
the return type of the fields where somekind diferent between version 7 and
version 8.
Do you want any information, Logs or anything?
Note: I am not a Visual C programmer, but I can try do do some debug if you
need it.
Regards
Miguel Juan
----- Original Message -----
From: "Dave Page" <dpage@vale-housing.co.uk>
To: <pgsql-odbc@postgresql.org>
Sent: Friday, July 22, 2005 11:43 AM
Subject: [ODBC] New libpq driver snapshot
I've uploaded an update of the new libpq driver to
ftp://ftp.postgresql.org/pub/odbc/versions/snapshots/. It will appear on
the PostgreSQL website and ftp mirrors within a day or so.
This version fixes all known memory leaks and other issues found in the
first snapshot of the new libpq driver, except the threading issue I've
found when using transactions in ODBCBench.
*** It is essential that this version gets lots of testing in order to
ensure it is of production quality before we make a proper release, so
please take the time to test your applications with it! ***
To aid testing, this driver will install as PostgreSQL-libpq, and may be
installed in parallel with non-libpq versions of the driver.
Regards, Dave.
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
> -----Original Message----- > From: pgsql-odbc-owner@postgresql.org > [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Miguel Juan > Sent: 22 July 2005 11:26 > To: Dave Page; pgsql-odbc@postgresql.org > Subject: Re: [ODBC] New libpq driver snapshot > > Hello, > > I just tried the latest snapshot under BDE (Borland Database Engine) > environment and the driver still have the same problems with de > text/char/varchar fields. > > With version 8 not libpq the fields appear in blank, but now > it do not show > field at all. Some time ago I done some Log comparation and I > found out that > the return type of the fields where somekind diferent between > version 7 and > version 8. Hello, Could you try the new version of the driver (psqlodbclibpq-08_01_003.zip) from http://www.postgresql.org/ftp/odbc/versions/snapshots/ and let us know if it fixes the problem please? Thanks, Dave.
> -----Original Message----- > From: Miguel Juan [mailto:mjuan@cibal.es] > Sent: 05 August 2005 15:51 > To: Dave Page > Subject: Re: [ODBC] New libpq driver snapshot > > Hello Dave, > > I attach the file "mylog_2688.log" for the gdcolas table test and > for the table "gdabs" you have mylog_3856.log file Hi Miguel, [Using Borland SQL Explorer] I've looked into this, and as far as I can tell, the driver is doing everything correctly. When you view the table contents using SELECT * FROM gdcolas, SQL Explorer basically does the following: - Executes the query using SQLExecDirectW - Looks at the columns using SQLDescribeColW, and for two columns sees SQL_C_Wxxx types. - Binds to all columns using SQLBindCol - Fetches data using SQLExtendedFetch, in SQL_C_CHAR format (which the driver duly converts and supplies) At which point it then appears to ignore the Unicode columns entirely. When you simply view the data in the table, it does it in exactly the same way *except* it doesn't execute SQLDescribeColW to describe the columns first. It seems to me like it is intentionally not displaying the Unicode columns, even though it has retrieved them as C strings. If it doesn't realise they're Unicode (because it didn't check first), it happily displays them. Unfortunately this means one of two things; either there is a bug in SQL Explorer, or, the driver is doing something so subtly wrong that I just can't see it. Either way, I don't think there's much else I can do I'm afraid. Perhaps one of the guys from Pervasive has an idea?? Regards, Dave.