Re: Updateable cursors - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Updateable cursors
Date
Msg-id 18474.1169564117@sss.pgh.pa.us
Whole thread Raw
In response to Re: Updateable cursors  ("Simon Riggs" <simon@2ndquadrant.com>)
Responses Re: Updateable cursors  ("Simon Riggs" <simon@2ndquadrant.com>)
List pgsql-hackers
"Simon Riggs" <simon@2ndquadrant.com> writes:
> On Wed, 2007-01-24 at 02:42 +1100, FAST PostgreSQL wrote:
>> In the UPDATE or DELETE statements the ‘WHERE CURRENT OF <cursor_name>’ 
>> clause results in the cursor name being placed in the UpdateStmt or 
>> DeleteStmt structure. During the processing of the functions - 
>> transformDeleteStmt() and transformUpdateStmt() - the cursor name is used to 
>> obtain a pointer to the related Portal structure 

> To support prepared statements we'd need to do this name lookup just
> once, so that the Update/Delete stmt can record which Portal to look at
> for the current tuple.

This really isn't gonna work, because it assumes that the tuple that is
"current" at the instant of parsing is still going to be "current" at
execution time.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: msvc failure in largeobject regression test
Next
From: Tom Lane
Date:
Subject: Re: regular expressions stranges