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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Cc: bruce(at)momjian(dot)us (Bruce Momjian), pgsql-hackers(at)postgresql(dot)org
Subject: Re: Any reason not to return row_count in cursor of plpgsql?
Date: 2009-03-27 19:04:08
Message-ID: 2592.1238180648@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-03-27 20:01:18 Re: Solaris getopt_long and PostgreSQL
Previous Message Tom Lane 2009-03-27 18:59:23 Re: Error message and infinite date and timestamp conversion in XML