Re: [HACKERS] FETCH without FROM/IN
От | Michael Meskes |
---|---|
Тема | Re: [HACKERS] FETCH without FROM/IN |
Дата | |
Msg-id | 20000113084816.A7433@fam-meskes.de обсуждение исходный текст |
Ответ на | Re: [HACKERS] FETCH without FROM/IN (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [HACKERS] FETCH without FROM/IN
|
Список | pgsql-hackers |
On Wed, Jan 12, 2000 at 08:13:02PM -0500, Tom Lane wrote: > I think, though, that you could make our syntax work like > FETCH [ opt_direction fetch_how_many FROM/IN ] portal_name > without conflicts. That'd be good since it'd be more like SQL92. Yes. I just read the patch I got from Rene in detail and it seems to implement: FETCH [ <direction> [ <fetch_how_many> ]] [ FROM/IN ] portal_name; Both direction and fetch_how_many are no longer optional in that they could be replaced by an empty string I wonder if this is correct. It would mean that we have to specify an amount resp. all everytime we do give a direction. However, I think it should be possible to make it: FETCH [ <direction> ][ <fetch_how_many> ] [ FROM/IN ] portal_name; This seems better, isn't it? 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@Fam-Meskes.De | Use PostgreSQL!
В списке pgsql-hackers по дате отправления: