Re: CURRENT OF cursor without OIDs

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ian Lance Taylor <ian(at)airs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: CURRENT OF cursor without OIDs
Date: 2001-08-07 18:01:07
Message-ID: 8675.997207267@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ian Lance Taylor <ian(at)airs(dot)com> writes:
> Anyhow, I see that there is a move afoot to eliminate mandatory OIDs.
> My question now is: if there is no OID, is there any comparable way to
> implement CURRENT OF cursor? Basically what is needed is some way to
> identify a particular row between a SELECT and an UPDATE.

I'd look at using TID. Seems like that is more efficient anyway (no
index needed). Hiroshi has opined that TID is not sufficient for ODBC
cursors, but it seems to me that it is sufficient for SQL cursors.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-08-07 18:10:04 Re: Recovery error
Previous Message Doug McNaught 2001-08-07 17:43:04 Re: Client Side Connection Pooling