Date: Tue, 2 Aug 2005 21:04:29 +0200
From: Roman Neuhauser <neuhauser@sigpipe.cz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-docs@postgresql.org
Subject: Re: "FETCH returns data as if it were a SELECT result"
Message-ID: <20050802190429.GA7082@isis.sigpipe.cz>
Mail-Followup-To: Tom Lane <tgl@sss.pgh.pa.us>,
	pgsql-docs@postgresql.org
References: <20050802153248.GA5320@isis.sigpipe.cz>
	<11939.1123002598@sss.pgh.pa.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <11939.1123002598@sss.pgh.pa.us>
User-Agent: Mutt/1.5.9i

# tgl@sss.pgh.pa.us / 2005-08-02 13:09:58 -0400:
> Roman Neuhauser <neuhauser@sigpipe.cz> writes:
> > "The variant of FETCH described here returns the data as if it were a
> > SELECT result rather than placing it in host variables."
> 
> > That doesn't seem to be the case.
> 
> It means it returns data *to the client* in the same way a SELECT does.

    Ok, and what does *that* mean? If you spend a few minutes on an
    explanation, I'll submit a patch to the documentation.

-- 
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man.  You don't KNOW.
Cause you weren't THERE.             http://bash.org/?255991