| From: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
|---|---|
| To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: psql's \d commands --- end of the line for |
| Date: | 2002-12-10 04:55:38 |
| Message-ID: | 20021210045538.GB20231@dcc.uchile.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Tue, Dec 10, 2002 at 12:55:51PM +1100, Philip Warner wrote:
> At 01:22 PM 9/12/2002 -0800, Christopher Kings-Lynne wrote:
> >Hmmm...I'm not certain that the \d commands really NEED to have a logical
> >link to the actual thing you're listing.
>
> This is the perspective a person with good memory, unlike me. In find it
> useful to be able to derive commands from common-sense rules, even if it
> means a little more typing.
Would it work to make \d tab-completable in a way that showed both the
commands that are available and the objects they describe? e.g.
\d<tab> would show something like
\dt [tables] \ds [sequences] \dv [views] ...
(the way it's shown now shows what completions are available, but not
what they mean. Also, both \d and \D should be shown in any case)
--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"Los romanticos son seres que mueren de deseos de vida"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Clift | 2002-12-10 05:24:13 | Re: [HACKERS] Let's create a release team |
| Previous Message | Nate Sommer | 2002-12-10 04:54:15 | Re: tuple descriptors? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Warner | 2002-12-10 06:16:26 | Re: psql's \d commands --- end of the line for |
| Previous Message | Joe Conway | 2002-12-10 03:48:13 | Re: proposal: array utility functions phase 1 |