Re: psql's \h MOVE - Mailing list pgsql-docs

From Robert Haas
Subject Re: psql's \h MOVE
Date
Msg-id BANLkTi=i=OFvkj0t_JK+0qvFwMi5db5_Jw@mail.gmail.com
Whole thread Raw
In response to Re: psql's \h MOVE  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: psql's \h MOVE  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-docs
On Sat, Apr 2, 2011 at 12:53 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Alvaro Herrera <alvherre@alvh.no-ip.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.

+1 for duplicating the definition.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-docs by date:

Previous
From: Robert Haas
Date:
Subject: Re: found a very confusing and maybe outdated sentence
Next
From: Robert Haas
Date:
Subject: Re: Migration page is out of date