Re: [HACKERS] FETCH without FROM/IN

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-13 07:48:16
Message-ID: 20000113084816.A7433@fam-meskes.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)Fam-Meskes(dot)De | Use PostgreSQL!

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas SB 2000-01-13 09:21:57 AW: [HACKERS] Re: Regress tests reveal *serious* psql bug
Previous Message Michael Robinson 2000-01-13 05:51:52 Re: [HACKERS] Copy from/to asymmetry