Any reason not to return row_count in cursor of plpgsql?

Any reason not to return row_count in cursor of plpgsql?

This is a discussion on Any reason not to return row_count in cursor of plpgsql? within the pgsql Hackers forums, part of the PostgreSQL category; --> hi all, I read the code that it seems easy for the cursor in plpgsql to return ROW_COUNT after ...

		Unix Technical Forum > Database Server Software > PostgreSQL > pgsql Hackers
Any reason not to return row_count in cursor of plpgsql?

#1 (permalink)

07-22-2008, 06:58 AM

laser

Posts: n/a

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 (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

« CommitFest dragging? | Re: WITH RECUSIVE patches 0721 »

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Posting Rules
You may not post new threads You may not post replies You may not post attachments You may not edit your posts vB code is On Smilies are On [IMG] code is On HTML code is Off Trackbacks are On Pingbacks are On Refbacks are On

Forum Jump

All times are GMT. The time now is 11:43 PM.