Re: psql's \h MOVE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Pg Docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: psql's \h MOVE
Date: 2011-04-02 16:53:08
Message-ID: 26889.1301763188@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> I just noticed that \h MOVE is particularly unhelpful:
> alvherre=# \h move
> Command: MOVE
> Description: position a cursor
> Syntax:
> MOVE [ direction { FROM | IN } ] cursorname

> The problem is that it doesn't specify what "direction" is. The doc
> text tells you to look into FETCH for details, but in \h you have to
> guess.

> We could fix this by including a note about fetch in the <synopsis>,
> so that it'd look like this:

> alvherre=# \h move
> Command: MOVE
> Description: position a cursor
> Syntax:
> MOVE [ direction [ FROM | IN ] ] cursor_name

> See FETCH for details on direction

-1 ... if this annoys you, just duplicate the definition of direction
from FETCH.

regards, tom lane

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Robert Haas 2011-04-03 23:51:46 Re: found a very confusing and maybe outdated sentence
Previous Message Heikki Linnakangas 2011-04-02 14:09:49 Re: fixed doc bug in sepgsql.sgml