Content-Type: text/plain; charset=UTF-8
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Pg Docs <pgsql-docs@postgresql.org>
Subject: Re: psql's \h MOVE
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Robert Haas <robertmhaas@gmail.com>
In-reply-to: <BANLkTi=i=OFvkj0t_JK+0qvFwMi5db5_Jw@mail.gmail.com>
References: <1301670352-sup-4920@alvh.no-ip.org>
	<26889.1301763188@sss.pgh.pa.us>
	<BANLkTi=i=OFvkj0t_JK+0qvFwMi5db5_Jw@mail.gmail.com>
Date: Mon, 04 Apr 2011 12:11:11 -0400
Message-Id: <1301933131-sup-7414@alvh.no-ip.org>
User-Agent: Sup/git
Content-Transfer-Encoding: 8bit

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@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.

> > -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@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support