Обсуждение: 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};
DATABASE=mybase;SERVER=myserver;PORT=5432;SSLMODE=prefer;
UID=postgres;PWD=postgres;ReadOnly=0;Protocol=6.4;FakeOidIndex=0;ShowOidColumn=1;RowVersioning=1;
ShowSystemTables=0;ConnSettings=;Fetch=100;Socket=4096;UnknownSizes=0;MaxVarcharSize=254;
MaxLongVarcharSize=8190;Debug=1;CommLog=1;Optimizer=1;Ksqo=3;UseDeclareFetch=0;TextAsLongVarchar=1;
UnknownsAsLongVarchar=0;BoolsAsChar=1;Parse=0;CancelAsFreeStmt=0;ExtraSysTablePrefixes=dd_;
LFConversion=1;UpdatableCursors=1;DisallowPremature=0;TrueIsMinus1=0;BI=0;ByteaAsLongVarBinary=0;
UseServerSidePrepare=0;LowerCaseIdentifier=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=mybase;SERVER=myserver;
PORT=5432;SSLMODE=prefer;UID=postgres;PWD=xxxxxxxx;ReadOnly=0;
Protocol=6.4;FakeOidIndex=0;ShowOidColumn=1;RowVersioning=1;ShowSystemTables=0;C
onnSettings=;Fetch=100;Socket=4096;UnknownSizes=0;MaxVarcharSize=254;MaxLongVarc
harSize=8190;Debug=1;CommLog=1;Optimizer=1;Ksqo=3;UseDeclareFetch=0;TextAsLongVa
rchar=1;UnknownsAsLongVarchar=0;BoolsAsChar=1;Parse=0;CancelAsFreeStmt=0;ExtraSy
sTablePrefixes=dd_;LFConversion=1;UpdatableCursors=1;DisallowPremature=0;TrueIsM
inus1=0;BI=0;ByteaAsLongVarBinary=0;UseServerSidePrepare=0;LowerCaseIdentifier=0
'
DESCRIPTOR ERROR: func=PGAPI_SetDescField, desc='', errnum=11,
errmsg='bad param
eter number'
I hope you can help me.
Thanks in advance.
Thomas Chabaud
> -----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.
> -----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 adLockBatchOptimistic are the culprits. They will only work with adOpenForwardOnly. adLockPessimistic or adLockReadOnly seem to work OK with any cursor type. Regards, Dave
> -----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 ? > > > > > -----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 > adLockBatchOptimistic 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.
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 ?
>
>
>
> > -----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
> adLockBatchOptimistic 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
Dave Page a écrit : > > > >>-----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 ? >> >> >> >> >>>-----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 >>adLockBatchOptimistic 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 > > Thanks a lot for your quick answer. It works well with UpdateableCursors=0; Regards, Thomas