| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Thom Brown <thombrown(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SHOW TABLES |
| Date: | 2010-07-15 16:43:48 |
| Message-ID: | AANLkTilphFfME3k4FJ2__GuLjvtf75nAeyCOB4t8okEl@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 15, 2010 at 18:35, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On Thu, 2010-07-15 at 17:38 +0200, Magnus Hagander wrote:
>
>> Is there an actual common use-case for having these commands available
>> for *non-psql* interfaces?
>
> There are many interfaces out there and people writing new ones
> everyday. We just wrote an interface for Android, for example.
>
> It is arguably *more* important to do this from non-psql interfaces.
>
> There should be one command to "display a list of tables" and it needs
> to be easily guessable for those who have forgotten.
The downside is that you are then limited to what can be returned as a
resultset. A "\d table" in psql returns a hell of a lot more than
that. So do we keep two separate formats for this? Or do we remove the
current, useful, output format in favor of a much worse formt just to
support more clients?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2010-07-15 16:48:12 | Re: SHOW TABLES |
| Previous Message | Simon Riggs | 2010-07-15 16:42:30 | Re: SHOW TABLES |