From: | "Jaime Casanova" <systemguards(at)gmail(dot)com> |
---|---|
To: | "FAST PostgreSQL" <fastpgs(at)fast(dot)fujitsu(dot)com(dot)au> |
Cc: | pgsql-patches(at)postgresql(dot)org |
Subject: | Re: Updateable cursors patch |
Date: | 2007-05-18 04:28:34 |
Message-ID: | c2d9e70e0705172128x34cb7ca1v8a410be8ec16fcb1@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
On 5/17/07, Jaime Casanova <systemguards(at)gmail(dot)com> wrote:
> On 5/17/07, FAST PostgreSQL <fastpgs(at)fast(dot)fujitsu(dot)com(dot)au> 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
Attachment | Content-Type | Size |
---|---|---|
tests.sql | application/octet-stream | 1.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2007-05-18 04:53:52 | Re: Maintaining cluster order on insert |
Previous Message | Jaime Casanova | 2007-05-18 04:25:20 | Re: Updateable cursors patch |