Re: psql's \d commands --- end of the line for - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: psql's \d commands --- end of the line for
Date
Msg-id 1039469112.1960.4.camel@rh72.home.ee
Whole thread Raw
In response to psql's \d commands --- end of the line for 1-character identifiers?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: psql's \d commands --- end of the line for
List pgsql-hackers
Tom Lane kirjutas T, 10.12.2002 kell 02:05:
> [ moved to hackers from pgsql-patches ]
> 
> "Christopher Kings-Lynne" <chriskl@familyhealth.com.au> writes:
> > Peter wrote:
> >> Christopher Kings-Lynne writes:
> >>> \dc - list conversions [PATTERN]
> >>> \dC - list casts
> >> 
> >> What are we going to use for collations?
> 
> > \dn   Is the only letter left in collations that hasn't been used!
> 
> ... and that was already proposed for "show schemas" (namespaces).
> 
> I'm inclined to think it's time to bite the bullet and go over to
> words rather than single characters to identify the \d target
> (viz, "\dschema", "\dcast", etc, presumably with unique abbreviations
> being allowed, as well as special cases for the historical single
> characters).
> 
> The issue here is what do we do with the existing "\d[istvS]" behavior
> (for instance, "\dsit" means "list sequences, indexes, and tables").
> Is that useful enough to try to preserve, or do we just bit-bucket it?
> If we do try to preserve it, how should it work?

Why not use \D for "long" ids ?

Somewhat similar to -? and --help for command line.

-- 
Hannu Krosing <hannu@tm.ee>


pgsql-hackers by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: Re: psql's \d commands --- end of the line for 1-character identifiers?
Next
From: Bruce Momjian
Date:
Subject: Re: Darwin/Mac OS X Startup Script