Re: Bug with version 08.01.0100 ?

Dave Page a écrit :
>
>
>
>>-----Original Message-----
>>From: pgsql-odbc-owner(at)postgresql(dot)org
>>[mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Dave Page
>>Sent: 07 November 2005 11:13
>>To: tc(at)geosys(dot)com; pgsql-odbc(at)postgresql(dot)org
>>Subject: Re: [ODBC] Bug with version 08.01.0100 ?
>>
>>
>>
>>
>>>-----Original Message-----
>>>From: pgsql-odbc-owner(at)postgresql(dot)org
>>>[mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Dave Page
>>>Sent: 07 November 2005 10:55
>>>To: tc(at)geosys(dot)com; pgsql-odbc(at)postgresql(dot)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