Re: Bug with version 08.01.0100 ?
От | Thomas Chabaud |
---|---|
Тема | Re: Bug with version 08.01.0100 ? |
Дата | |
Msg-id | 436F5481.6010204@geosys.com обсуждение исходный текст |
Ответ на | Re: Bug with version 08.01.0100 ? ("Dave Page" <dpage@vale-housing.co.uk>) |
Список | pgsql-odbc |
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
В списке pgsql-odbc по дате отправления: