Re: psql \d option list overloaded

From: Jon Jensen <jon(at)endpoint(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: psql \d option list overloaded
Date: 2004-01-11 00:16:58
Message-ID: Pine.LNX.4.58.0401110014230.1302@louche.swelter.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-general pgsql-hackers

On Sat, 10 Jan 2004, Tom Lane wrote:

> ISTM there are three fundamental problems with \d and friends:
>
> 1. Some people have a hard time remembering the commands.
> 2. Some people aren't using psql.
> 3. psql keeps breaking across backend versions because the
> needed commands change.
>
> I don't see a lot of value in addressing just one of these problem
> areas, when we could instead do something that addresses all three.

I agree, at least for #2 and #3. But I just don't understand #1. Anything
is hard to remember when you're just starting to learn it. But it's still
faster to type \? <CR> then \dt than it is to type "show tables". And
"show tables" is hard (relatively speaking) for me to remember because I'm
used to psql's way of doing things, since I mostly use it.

Jon

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Peter Eisentraut 2004-01-11 01:07:25 Re: psql \d option list overloaded
Previous Message Tom Lane 2004-01-10 19:15:19 Re: psql \d option list overloaded

Browse pgsql-general by date

  From Date Subject
Next Message Igor Shevchenko 2004-01-11 00:54:05 psql's "\d" and CLUSTER
Previous Message Thomas Kellerer 2004-01-11 00:07:08 Re: Any way to SELECT a list of table names?

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2004-01-11 01:07:25 Re: psql \d option list overloaded
Previous Message Hannu Krosing 2004-01-10 23:03:04 Re: Encoding problems in PostgreSQL with XML data