Re: Cursor Error - Mailing list pgsql-general

From Bob Pawley
Subject Re: Cursor Error
Date
Msg-id 007501c8f339$bc445760$6401a8c0@owner
Whole thread Raw
In response to Cursor Error  ("Bob Pawley" <rjpawley@shaw.ca>)
Responses Re: Cursor Error
List pgsql-general
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@sss.pgh.pa.us>
To: "Bob Pawley" <rjpawley@shaw.ca>
Cc: "PostgreSQL" <pgsql-general@postgresql.org>
Sent: Thursday, July 31, 2008 9:50 AM
Subject: Re: [GENERAL] Cursor Error


> "Bob Pawley" <rjpawley@shaw.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@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general


pgsql-general by date:

Previous
From: David R Robison
Date:
Subject: Re: Doing an LDAP lookup from a SQL SELECT
Next
From: Magnus Hagander
Date:
Subject: Re: Doing an LDAP lookup from a SQL SELECT