| From: | Roman Neuhauser <neuhauser(at)sigpipe(dot)cz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: "FETCH returns data as if it were a SELECT result" |
| Date: | 2005-08-02 19:04:29 |
| Message-ID: | 20050802190429.GA7082@isis.sigpipe.cz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
# tgl(at)sss(dot)pgh(dot)pa(dot)us / 2005-08-02 13:09:58 -0400:
> Roman Neuhauser <neuhauser(at)sigpipe(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Norm Costa | 2005-08-02 19:39:23 | unsubscribe |
| Previous Message | Tom Lane | 2005-08-02 17:09:58 | Re: "FETCH returns data as if it were a SELECT result" |