From: | Dennis Björklund <db(at)zigo(dot)dhs(dot)org> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Kevin Brown <kevin(at)sysexperts(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql \d option list overloaded |
Date: | 2004-01-10 16:27:21 |
Message-ID: | Pine.LNX.4.44.0401101720500.13405-100000@zigo.dhs.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-general pgsql-hackers |
On Sat, 10 Jan 2004, Peter Eisentraut wrote:
> > to remember way of showing the various entities in psql (at the very
> > least) would be of great advantage. It's something that MySQL gets
> > right. As it turns out, we already have "SHOW" in psql and it's used
> > for something else.
>
> What is wrong with
>
> SELECT * FROM information_schema.tables;
The result is very hard to read since it's so much of it (try column
instead of tables). The \xx commands do some nice formatting you don't
get from the above.
I would rather have long commands so one can write
\describe_table foo
and have the tab completion work for these of course (only for the long
commands, the \dt and such does not belong in completion).
The information schema is nice, but it's not what I want to use at the
prompt to view the content of the database.
--
/Dennis Björklund
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2004-01-10 18:22:11 | Re: Will Open Source be forced to go Proprietary |
Previous Message | Peter Eisentraut | 2004-01-10 13:07:24 | Re: psql \d option list overloaded |
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 2004-01-10 16:36:56 | Re: Hierarchical queries |
Previous Message | Anton.Nikiforov | 2004-01-10 15:50:16 | Re: Hierarchical queries |
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2004-01-10 17:41:12 | Re: OLE DB driver |
Previous Message | Peter Eisentraut | 2004-01-10 13:07:24 | Re: psql \d option list overloaded |