| From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, 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 21:59:33 |
| Message-ID: | 2CB5C1EB-6860-47D7-8DC0-D119E157F696@hi-media.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Le 15 juil. 2010 à 18:43, Magnus Hagander <magnus(at)hagander(dot)net> a écrit :
> 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?
I think we should keep both, and optionaly have a given psql \d command issue more than one SHOW query. Same as it does now with SELECT queries.
That means we keep a resultset per SHOW query, so it's easy on the application.
Regards,
--
dim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2010-07-15 22:09:41 | buildfarm owners, please add REL9_0_STABLE to your list of builds |
| Previous Message | Simon Riggs | 2010-07-15 21:46:42 | Re: SHOW TABLES |