Postgres Pro
Downloads
Home   >   mailing lists

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

From laser
Subject Any reason not to return row_count in cursor of plpgsql?
Date
Msg-id 4883E8EA.6020702@pgsqldb.com
Whole thread Raw
Responses Re: Any reason not to return row_count in cursor of plpgsql?  (Bruce Momjian <bruce@momjian.us>)
Re: Any reason not to return row_count in cursor of plpgsql?  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Tree view 
hi all,
I read the code that it seems easy for the cursor in plpgsql to return 
ROW_COUNT afterMOVE LAST etc. The SPI_processed variable already there, but didn't put 
it into estatestructure, any reason for that?
thanks and best regards
-laser

pgsql-hackers by date:

Previous
From: "Radek Strnad"
Date:
Subject: Re: [WIP] collation support revisited (phase 1)
Next
From: Tom Lane
Date:
Subject: Re: TODO item: Have psql show current values for a sequence