Re: Bug with version 08.01.0100 ? - Mailing list pgsql-odbc

From Dave Page
Subject Re: Bug with version 08.01.0100 ?
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E4CC398D@ratbert.vale-housing.co.uk
Whole thread Raw
In response to Bug with version 08.01.0100 ?  (Thomas Chabaud <tc@geosys.com>)
Responses Re: Bug with version 08.01.0100 ?
Re: Bug with version 08.01.0100 ?
List pgsql-odbc

> -----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.

pgsql-odbc by date:

Previous
From: "Dave Page"
Date:
Subject: Re: Bug with version 08.01.0100 ?
Next
From: Thomas Chabaud
Date:
Subject: Bug with version 08.01.0100 ?