[Oledb-dev] Using PostgreSQL OLEDB with LabSQL (a LabView ADO wrapper)

[Sílvio Macedo]

Dear list, 

I'm using PostgreSQL 8.0.3 with OLEDB 1.0.19 on Windows XP Pro SP2.

Client is ADO activex MDAC 2.8 (or whatever is the default XP SP2)
(wrapped by LabSQL, a library for LabView, an IDE for instrumentation
and control).

While using LabSQL with the following OLEDB connection string:

Provider=PostgreSQL.1;Password=xxxxx;User ID=IT2CalMeter;
Data Source="";Location=IT2CalMeter2005;Extended Properties=""

if a SQL Execute command fails, (for example, "BADSELECT * from xx"
instead of "SELECT * from xx"), then, calling ADO activex
Connection.Close does not close the connection to the backend - it
stays there forever. (I can list it using pgAdmin III monitor "Server
Status" tool)


If, instead, I use the following __ODBC__ connection string:

DRIVER={PostgreSQL};SERVER=127.0.0.1;port=5432;DATABASE=IT2CalMeter200
5;UID=IT2CalMeter;PWD=xxxxx;

then all works fine and the backend won't have left over connections
any longer.

My guess is that OLEDB internal state after an error compromises it
being able to properly close connection.

In the OLEDB log, I don't see any warning or error, except for the
obvious syntax error. 

For now, I'll be using ODBC, but it would be great to do OLEDB
directly.
Thanks!

Silvio