| From: | Michael Meskes <meskes(at)postgreSQL(dot)org> |
|---|---|
| To: | PostgreSQL Hacker <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] FETCH without FROM/IN |
| Date: | 2000-01-12 16:53:26 |
| Message-ID: | 20000112175326.A2376@fam-meskes.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 12, 2000 at 11:09:11AM -0500, Tom Lane wrote:
> It looks to me like the backend grammar *does* accept FETCH without
> IN/FROM cursor. Which seems pretty bizarre --- I don't understand how
> it makes sense to omit a cursor name from FETCH.
Yes, it does accept if NO portal name is given. This is corrected by the
patch. But what I wanted to talk about is the IN/FROM keyword.
> <fetch statement> ::=
> FETCH [ [ <fetch orientation> ] FROM ]
> <cursor name> INTO <fetch target list>
To me this seems to say that FROM is just optional. Okay, if I make it
optional in our parser?
Michael
--
Michael Meskes | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz | Go Rhein Fire!
Tel.: (+49) 2431/72651 | Use Debian GNU/Linux!
Email: Michael(at)Fam-Meskes(dot)De | Use PostgreSQL!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Meskes | 2000-01-12 16:56:37 | Re: [HACKERS] FETCH without FROM/IN |
| Previous Message | Thomas Lockhart | 2000-01-12 16:43:07 | Re: [HACKERS] FETCH without FROM/IN |