| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> | 
|---|---|
| To: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> | 
| Cc: | pgsql-patches(at)postgresql(dot)org | 
| Subject: | Re: updateable cursors | 
| Date: | 2003-07-31 04:39:11 | 
| Message-ID: | 200307310439.h6V4dBY04204@candle.pha.pa.us | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-patches | 
Can I get some comments on this?  I know the work was completed
pre-feature freeze, but submitted only recently.
---------------------------------------------------------------------------
Gavin Sherry wrote:
> Attached is a patch implementing updatable cursors in HEAD. Regression
> test and documentation are included.
> 
> Updateable cursors are used as follows:
> 
> begin;
> declare foo cursor for select * from bar for update;
> fetch foo;
> update bar set abc='def' where current of foo;
> fetch foo;
> delete from bar where current of foo;
> commit;
> 
> 
> Two points:
> 
> i) The patch doesn't implement updateable cursors for cursors marked WITH
> HOLD. I have working code for this and will send it in soon.
> 
> ii) I've implemented a new snapshot type since, AFAICT, updateable cursors
> have a type of tuple visibility. Namely, if the base table of a cursor is
> updated based on that cursor, the new and old tuples are removed from the
> cursor's set of visible tuples. Like wise, deleted tuples are also
> removed.
> 
> Thanks,
> 
> Gavin
Content-Description:
[ Attachment, skipping... ]
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend
-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-07-31 04:48:35 | Re: Spelling fix | 
| Previous Message | Tom Lane | 2003-07-31 04:13:19 | Re: hexadecimal to decimal |