| From: | Thom Brown <thombrown(at)gmail(dot)com> |
|---|---|
| To: | "Marc G(dot) Fournier" <scrappy(at)hub(dot)org> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SHOW TABLES |
| Date: | 2010-07-15 16:09:32 |
| Message-ID: | AANLkTik4Uuz8b75Xq9TH-lrrhT6qOnii2h4bnwlluID-@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 15 July 2010 17:07, Marc G. Fournier <scrappy(at)hub(dot)org> wrote:
> On Thu, 15 Jul 2010, Thom Brown wrote:
>
>> If it's only a psql problem, why implement it as SQL? Is it just so we're
>> not adding keywords specifically to psql? In that case, it shouldn't
>> support QUIT.
>
> Personally, I think this is somethign that should go into the backend ...
> I'd like to be able to write perl scripts that talk to the backend without
> having to remember all the various system tables I need to query / join to
> get the same results as \d gives me in psql ... same for any interface
> language, really ...
>
Isn't that what the information_schema catalog is for?
Thom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-07-15 16:10:35 | Re: SHOW TABLES |
| Previous Message | Marc G. Fournier | 2010-07-15 16:07:22 | Re: SHOW TABLES |