g number of selected rows into a temp
> >> table
> >> in 7.4.5 GET DIAGNOSTICS returns 0
> >
> >
>
> Hmm. I'm not sure if that's a bug or an improvement. The command did
> not return any rows to plpgsql, so in that sense row_count = 0 is
> correct, but I c
e have an opinion about this?
regards, tom lane
--------------------------------
Subject:
Re: [GENERAL] Get diagnistic (row_count) 7.3 vs. 7.4 changes
From:
"Richard Huxton" <[EMAIL PROTECTED]>
Date:
Thu, 2 Dec 2004 01:34:37 -0800
To:
"Tom Lane" <[EM
Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, December 01, 2004 5:53 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: [GENERAL] Get diagnistic (row_count) 7.3 vs. 7.4 changes
>
>
> Maksim Likharev <[EMAIL PROTECTED]> writes:
> > consider
Tom Lane wrote:
Maksim Likharev <[EMAIL PROTECTED]> writes:
in 7.3.3 GET DIAGNOSTICS was returning number of selected rows into
a temp table in 7.4.5 GET DIAGNOSTICS returns 0
Hmm. I'm not sure if that's a bug or an improvement. The command
did not return any rows to plpgsql, so in that sense ro
Maksim Likharev <[EMAIL PROTECTED]> writes:
> consider following code:
> CREATE OR REPLACE FUNCTION rowcount_test() RETURNS bigint AS '
> DECLARE
> base_hits bigint;
> BEGIN
> CREATE TEMP TABLE ltbl_temp AS SELECT 1 AS data;
> GET DIAGNOSTICS base_hits = ROW_COUNT;
> RETURN base
Hi,
Just trying 7.4.5 and bumped into a problem.
consider following code:
CREATE OR REPLACE FUNCTION rowcount_test() RETURNS bigint AS '
DECLARE
base_hits bigint;
BEGIN
CREATE TEMP TABLE ltbl_temp AS SELECT 1 AS data;
GET DIAGNOSTICS base_hits = ROW_COUNT;
RETURN base_hits;
E
