Tom Lane wrote:
> It's interesting to note that "help", "\h", and "\?" all provoke the
> same response(s) in mysql. Perhaps a patch that had had more than two
> seconds' design effort in it would do the same in psql; though I'm not
> sure what to do to disambiguate the case with no arguments.
I'm not sure that plain \? and \h output is all that useful. If you
can understand what to make from that, you wouldn't be using "help" in
the first place. I think a more extensive text would be more
appropriate, which referenced the \? and \h commands so that the user
could take a peek after reading the blurb.
To avoid the usage of unadorned "help" (which I don't think is going to
ever cause conflicts with a SQL command but perhaps it's better to be
prepared), one idea would be to respond with "please execute \help
instead", and then \help would emit the verbose output. Perhaps
eventually we could adorn it with "\help category", etc.
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
In response to
pgsql-hackers by date
|Next:||From: Alvaro Herrera||Date: 2008-01-20 19:55:19|
|Subject: bgwriter_lru_multiplier blurbs inconsistent|
|Previous:||From: Simon Riggs||Date: 2008-01-20 19:31:41|
|Subject: Re: Transaction Snapshot Cloning|
pgsql-patches by date
|Next:||From: Greg Sabino Mullane||Date: 2008-01-20 20:32:10|
|Subject: Re: Friendly help for psql|
|Previous:||From: Tom Lane||Date: 2008-01-20 19:08:42|
|Subject: Re: Friendly help for psql |