PostgeSQL ODBC - Bug with version 08.01.0100 ?

Author

Bug with version 08.01.0100 ?

Thomas Chabaud

2005-11-08, 9:24 am

I have installed the new version of the Postgre ODBC driver with the msi
installer provided, but I have a Visual Basic abnormal error when I try
to open a recordset.

The conn.open works without problem, the error happens only when I try
to open the recordset with the following code :

Dim rs As New ADODB.Recordset
Dim sqlStr as String

sqlStr = "SELECT * FROM tUsers"
rs.Open sqlStr, dbConn, adOpenStatic, adLockOptimistic, adCmdText

- My conn.ConnectionString is :

Provider=MSDASQL.1;Extended Properties="DRIVER={PostgreSQL-libpq};
DATABASE=mybase;SERV
ER=myserver;PORT=543
2;SSLMODE=prefer;
UID=postgres;PWD=pos
tgres;ReadOnly=0;Pro
tocol=6. 4;FakeOidIndex=0;Sho
wOidColumn=1;RowVers
ioning=1;
ShowSystemTables=0;C
onnSettings=;Fetch=1
00;Socket=4096;Unkno
wnSizes=0;MaxVarchar
Size=254;
MaxLongVarcharSize=8
190;Debug=1;CommLog=
1;Optimizer=1;Ksqo=3
;UseDeclareFetch=0;T
extAsLongVarchar=1;
UnknownsAsLongVarcha
r=0;BoolsAsChar=1;Pa
rse=0;CancelAsFreeSt
mt=0;ExtraSysTablePr
efixes=dd_;
LFConversion=1;Updat
ableCursors=1;Disall
owPremature=0;TrueIs
Minus1=0;BI=0;ByteaA
sLongVarBinary=0;
UseServerSidePrepare
=0;LowerCaseIdentifi
er=0"

- And here is the log :

[ PostgreSQL version string = 'PostgreSQL 8.0.4 on i686-pc-mingw32,
compiled
by GCC gcc.exe (GCC) 3.4.2 (mingw-special)' ]
[ PostgreSQL version number = '8.0' ]
conn=131349608, query='set DateStyle to 'ISO''
conn=131349608, query='set geqo to 'OFF''
conn=131349608, query='set extra_float_digits to 2'
conn=131349608, query='select oid from pg_type where typname='lo''
[ Large Object oid = 17612 ]
conn=131349608, query='select pg_client_encoding()
'
[ Client encoding = 'SQL_ASCII' (code = 0) ]
conn=131349608,
PGAPI_DriverConnect(
out)='DRIVER={PostgreSQL- libpq};DATABASE=myba
se;SERVER=myserver;
PORT=5432;SSLMODE=pr
efer;UID=postgres;PW
D=xxxxxxxx;ReadOnly=
0;
Protocol=6. 4;FakeOidIndex=0;Sho
wOidColumn=1;RowVers
ioning=1;ShowSystemT
ables=0;C
onnSettings=;Fetch=1
00;Socket=4096;Unkno
wnSizes=0;MaxVarchar
Size=254;MaxLongVarc

harSize=8190;Debug=1
;CommLog=1;Optimizer
=1;Ksqo=3;UseDeclare
Fetch=0;TextAsLongVa

rchar=1;UnknownsAsLo
ngVarchar=0;BoolsAsC
har=1;Parse=0;Cancel
AsFreeStmt=0;ExtraSy

sTablePrefixes=dd_;L
FConversion=1;Updata
bleCursors=1;Disallo
wPremature=0;TrueIsM

inus1=0;BI=0;ByteaAs
LongVarBinary=0;UseS
erverSidePrepare=0;L
owerCaseIdentifier=0

'
DESCRIPTOR ERROR: func=PGAPI_SetDescFi
eld, desc='', errnum=11,
errmsg='bad param
eter number'

I hope you can help me.

Thanks in advance.

Thomas Chabaud

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Dave Page

2005-11-08, 9:24 am

> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Thomas Chabaud
> Sent: 07 November 2005 10:39
> To: pgsql-odbc@postgresql.org
> Subject: [ODBC] Bug with version 08.01.0100 ?
>
> I have installed the new version of the Postgre ODBC driver
> with the msi
> installer provided, but I have a Visual Basic abnormal error
> when I try
> to open a recordset.
>
> The conn.open works without problem, the error happens only when I try
> to open the recordset with the following code :
>
>
> Dim rs As New ADODB.Recordset
> Dim sqlStr as String
>
> sqlStr = "SELECT * FROM tUsers"
> rs.Open sqlStr, dbConn, adOpenStatic, adLockOptimistic, adCmdText
>
> - My conn.ConnectionString is :
>
> Provider=MSDASQL.1;Extended Properties="DRIVER={PostgreSQL-libpq};

^^^^^^^^^^^^^^^^

That is an old snapshot of the driver - you should be using either:

DRIVER={PostgreSQL ANSI}

Or

DRIVER={PostgreSQL Unicode}

I've tried your connection string (modified for my local server of
course) and rs.Open (but with pg_class), and it does seem that only
adOpenForwardOnly and adOpenDynamic work as expected :-(. I'll open a
tracker about this.

Regards Dave.

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Dave Page

2005-11-08, 9:24 am

> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Dave Page
> Sent: 07 November 2005 10:55
> To: tc@geosys.com; pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] Bug with version 08.01.0100 ?
>
>
> I've tried your connection string (modified for my local server of
> course) and rs.Open (but with pg_class), and it does seem that only
> adOpenForwardOnly and adOpenDynamic work as expected :-(. I'll open a
> tracker about this.

Sorry - that's not quite right - it seems that adLockOptimistic or
adLockBatchOptimisti
c are the culprits. They will only work with
adOpenForwardOnly. adLockPessimistic or adLockReadOnly seem to work OK
with any cursor type.

Regards, Dave

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Dave Page

2005-11-08, 9:24 am

> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Dave Page
> Sent: 07 November 2005 11:13
> To: tc@geosys.com; pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] Bug with version 08.01.0100 ?
>
>
>
> I'll open a
>
> Sorry - that's not quite right - it seems that adLockOptimistic or
> adLockBatchOptimisti
c are the culprits. They will only work with
> adOpenForwardOnly. adLockPessimistic or adLockReadOnly seem to work OK
> with any cursor type.

PPS: This only appears to happen with UpdateableCursors enabled, which
is an experimental feature anyway.

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Leendert Paul Diterwich

2005-11-08, 9:24 am

Dear All,

Today again I got an empty odbc error message in my debugger after
installing the 08.01.01 version. Again I'm having great difficulties
replicating this. I there a way I can put the ODBC driver in a kind of debug
mode, that it writes a log what it is doing etc?

Regards,

Paul

-----Oorspronkelijk bericht-----
Van: pgsql-odbc-owner@postgresql.org
[mailto:pgsql-odbc-owner@postgresql.org] Namens Dave Page
Verzonden: maandag 7 november 2005 12:30
Aan: Dave Page; tc@geosys.com; pgsql-odbc@postgresql.org
Onderwerp: Re: [ODBC] Bug with version 08.01.0100 ?

> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Dave Page
> Sent: 07 November 2005 11:13
> To: tc@geosys.com; pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] Bug with version 08.01.0100 ?
>
>
>
> I'll open a
>
> Sorry - that's not quite right - it seems that adLockOptimistic or
> adLockBatchOptimisti
c are the culprits. They will only work with
> adOpenForwardOnly. adLockPessimistic or adLockReadOnly seem to work OK
> with any cursor type.

PPS: This only appears to happen with UpdateableCursors enabled, which
is an experimental feature anyway.

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Thomas Chabaud

2005-11-08, 9:24 am

Dave Page a écrit :
>
>
>
>
>
> PPS: This only appears to happen with UpdateableCursors enabled, which
> is an experimental feature anyway.
>
> Regards, Dave.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>
>

Thanks a lot for your quick answer.
It works well with UpdateableCursors=0;

Regards,

Thomas

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Sponsored Links