Re: psql's \h MOVE

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: psql's \h MOVE
Date: 2011-04-04 16:11:11
Message-ID: 1301933131-sup-7414@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Excerpts from Robert Haas's message of dom abr 03 20:37:39 -0400 2011:
> 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.

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

Done that way.

(I'd like to have something like \h column_constraint for common stuff
in ALTER TABLE and CREATE TABLE, but that'll have to wait.)

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Gabriele Bartolini 2011-04-04 16:23:57 Re: [HACKERS] Uppercase SGML entity declarations
Previous Message Tom Lane 2011-04-04 15:17:19 Re: EXTENSION keyword