Re: CTID: Anyway to lock it?

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: Jim Hines <jhines(at)wdtv(dot)com>
Cc: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, Andrea <aguarini(at)chyron(dot)com>, pgsql-odbc(at)postgresql(dot)org
Subject: Re: CTID: Anyway to lock it?
Date: 2002-11-06 00:12:09
Message-ID: 3DC85E59.2CEFA1A2@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Jim Hines wrote:
>
> > > Hmm, yes - it appears to be in inner_process_tokens(QueryParse *qp,
> > > QueryBuild *qb) in convert.c. I don't know what options might affect
> > > that though I'm afraid - do you know Hiroshi?
> >
> > The driver uses CTID and OID to implement updatable cursors.
> > Please turn off the *Updatable cursors* DSN option if you
> > don't like the behavior.
> >
> > regards,
> > Hiroshi Inoue
> > http://w2422.nsk.ne.jp/~inoue/
>
> If I turn off the cursors, the Lyric software complains about an Invalid
> Cursor state.

If the software requires keyset-driven/static cursors with
optimistic concurrency control, you may have to turn on the
option or need the help of e.g. ODBC cursor library.

regards,
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue/

In response to

Browse pgsql-odbc by date

  From Date Subject
Next Message Valerio Ferrucci 2002-11-06 16:36:49 Calling a function via ODBC
Previous Message Jim Hines 2002-11-05 15:35:22 Re: CTID: Anyway to lock it?