| From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
| Cc: | Jim Hines <jhines(at)wdtv(dot)com>, pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: CTID: Anyway to lock it? |
| Date: | 2002-11-05 10:04:33 |
| Message-ID: | 3DC797B1.761EB5D2@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
Dave Page wrote:
>
> > -----Original Message-----
> > From: Jim Hines [mailto:jhines(at)wdtv(dot)com]
> > Sent: 04 November 2002 20:06
> > To: pgsql-odbc(at)postgresql(dot)org; Dave Page
> > Subject: Re: [ODBC] CTID: Anyway to lock it?
> >
> > The folks at Chyron say they are not specifiing CTID and that
> > it must be
> > within the ODBC driver. Could this be the case? If so, what
> > setting would
> > control this?
>
> 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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Samuele | 2002-11-05 10:07:05 | Increase inactivity timeout |
| Previous Message | Tambet Matiisen | 2002-11-05 09:50:41 | updatable views and optimistic locking |