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

Thanks, patch applied. --- Andrew Gierth wrote: Bruce == Bruce Momjian br...@momjian.us writes: hi all, I read the code that it seems easy for the cursor in plpgsql to return ROW_COUNT after MOVE LAST etc.

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

Bruce == Bruce Momjian br...@momjian.us writes: 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

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

Andrew Gierth and...@tao11.riddles.org.uk writes: GET DIAGNOSTICS ROW_COUNT is documented as working for all commands; if it doesn't work for MOVE (and FETCH), that's a bug. Or a documentation problem. I don't see any claim that it works for all commands anyway.

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

Tom == Tom Lane t...@sss.pgh.pa.us writes: Andrew Gierth and...@tao11.riddles.org.uk writes: GET DIAGNOSTICS ROW_COUNT is documented as working for all commands; if it doesn't work for MOVE (and FETCH), that's a bug. Tom Or a documentation problem. I don't see any claim that it works

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

On Fri, Mar 27, 2009 at 08:59:29PM +, Andrew Gierth wrote: Tom == Tom Lane t...@sss.pgh.pa.us writes: Andrew Gierth and...@tao11.riddles.org.uk writes: GET DIAGNOSTICS ROW_COUNT is documented as working for all commands; if it doesn't work for MOVE (and FETCH), that's a bug.

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

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

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

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? [ Sorry for the delay.] Would some tests how Oracle

[HACKERS] Any reason not to return row_count in cursor of plpgsql?

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 -laser -- Sent via pgsql-hackers mailing list