Re: Any reason not to return row_count in cursor of plpgsql?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: laser <laserlist(at)pgsqldb(dot)com>
Cc: Postgres - Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Any reason not to return row_count in cursor of plpgsql?
Date: 2009-03-27 02:26:35
Message-ID: 200903270226.n2R2QZC10054@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

laser wrote:
> hi all,
>
> I read the code that it seems easy for the cursor in plpgsql to return
> ROW_COUNT after
> MOVE LAST etc. The SPI_processed variable already there, but didn't put
> it into estate
> structure, any reason for that?
>
> thanks and best regards

Sorry, we have decided against this change because it might break
existing applications.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2009-03-27 02:28:48 Re: typedefs for indent
Previous Message Bruce Momjian 2009-03-27 02:25:09 Re: 8.4 release notes proof reading 1/2