Re: Cursor Error
- From: "Bob Pawley" <rjpawley(at)shaw(dot)ca>
- To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: "PostgreSQL" <pgsql-general(at)postgresql(dot)org>
- Subject: Re: Cursor Error
- Date: Thu, 31 Jul 2008 11:17:44 -0700
- Message-id: <007501c8f339$bc445760$6401a8c0@owner> <text/plain>
Is it allowed to declare a cursor in this manner??
Declare
procgraphic cursor for select p_id.p_id.process_id from p_id.p_id,
processes_count
where p_id.p_id.p_id_id = processes_count.p_id_id;
Bob
----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Bob Pawley" <rjpawley(at)shaw(dot)ca>
Cc: "PostgreSQL" <pgsql-general(at)postgresql(dot)org>
Sent: Thursday, July 31, 2008 9:50 AM
Subject: Re: [GENERAL] Cursor Error
"Bob Pawley" <rjpawley(at)shaw(dot)ca> writes:
Right.
This is the cursor statement.
Open procgraphic for select p_id.p_id.process_id from p_id.p_id,
processes_count
where p_id.p_id.p_id_id = processes_count.p_id_id;
Sorry, we're not bright enough to handle WHERE CURRENT OF on a join
--- per the fine manual,
The cursor must be a simple (non-join, non-aggregate) query on
the UPDATE's target table.
I don't recall offhand whether there's some deep technical reason
for the restriction against joins, or we just didn't get around to
it. In any case, you'll need to change the cursor to return the
table's primary key and use that to target the UPDATE.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Home |
Main Index |
Thread Index