Re: Any reason not to return row_count in cursor of plpgsql? - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Any reason not to return row_count in cursor of plpgsql?
Date
Msg-id 200903270226.n2R2QZC10054@momjian.us
Whole thread Raw
In response to Any reason not to return row_count in cursor of plpgsql?  (laser <laserlist@pgsqldb.com>)
Responses Re: Any reason not to return row_count in cursor of plpgsql?  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List 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@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: 8.4 release notes proof reading 1/2
Next
From: Bruce Momjian
Date:
Subject: Re: typedefs for indent