Re: psql's \h MOVE

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Pg Docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: psql's \h MOVE
Date: 2011-04-04 00:37:39
Message-ID: BANLkTi=i=OFvkj0t_JK+0qvFwMi5db5_Jw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Sat, Apr 2, 2011 at 12:53 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.

+1 for duplicating the definition.

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

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Robert Haas 2011-04-04 00:38:55 Re: Migration page is out of date
Previous Message Robert Haas 2011-04-03 23:51:46 Re: found a very confusing and maybe outdated sentence