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: 2008-12-15 23:42:55
Message-ID: 200812152342.mBFNgtM27630@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?

[ Sorry for the delay.]

Would some tests how Oracle behaves in this case?

--
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

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2008-12-15 23:43:37 Re: [ADMIN] shared_buffers and shmmax
Previous Message Bruce Momjian 2008-12-15 23:41:41 Re: TODO item: Have psql show current values for a sequence