On 5/17/07, Jaime Casanova <[EMAIL PROTECTED]> wrote:
On 5/17/07, FAST PostgreSQL <[EMAIL PROTECTED]> wrote: > No. It works with scrollable cursors. It will work for cursors/selects > which does not put the results in some store, such as WITH hold/group > by/order by etc.... But most of these restrictions apply for normal > 'Select for update' anyway. (With the order by clause, the > implementation is as per the sql standards.) >your patch doesn't work with updatable views because they don't have ctid columns.... ERROR: column "ctid" does not exist STATEMENT: update vfoo set des_cta = des_cta || ' - prueba' where current of foo; ERROR: current transaction is aborted, commands ignored until end of transaction block is this sane behavior? to accept create cursors for update on views and then failing to update "where current of" and rollback the entire transaction? comments?
sorry, reattaching the test script -- regards, Jaime Casanova "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs and the universe trying to produce bigger and better idiots. So far, the universe is winning." Richard Cook
Description: Binary data
---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match