From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bill Cunningham <billc@ballydev.com>
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Schemas: status report, call for developers
Date: Tue, 30 Apr 2002 14:23:45 -0400
Message-ID: <21260.1020191025@sss.pgh.pa.us> (raw)
In-Reply-To: <3CCED849.5040400@ballydev.com>
References: <21020.1020187890@sss.pgh.pa.us>
<3CCED849.5040400@ballydev.com>
Bill Cunningham <billc@ballydev.com> writes:
> I would think this should produce the following:
> test=# \d mytab
> Table "bar.mytab"
> Column | Type | Modifiers
> --------+---------+-----------
> f1 | text |
> f1 | integer |
> Table "foo.mytab"
> Column | Type | Modifiers
> --------+---------+-----------
> f2 | text |
> f3 | integer |
Even when schemas bar and foo are not in your search path? (And,
perhaps, not even accessible to you?)
My gut feeling is that "\d mytab" should tell you about the same
table that "select * from mytab" would find. Anything else is
probably noise to you --- if you wanted to know about foo.mytab,
you could say "\d foo.mytab".
However, \d is not a wildcardable operation AFAIR. For the commands
that do take wildcard patterns (like \z), I'm not as sure what should
happen.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, billc@ballydev.com, pgsql-hackers@postgresql.org
Subject: Re: Schemas: status report, call for developers
In-Reply-To: <21260.1020191025@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox