From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Bernd Helmle <mailings(at)oopsware(dot)de>, Guillaume Lelarge <guillaume(at)lelarge(dot)info>, jd(at)commandprompt(dot)com, 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-16 12:49:06 |
Message-ID: | 201007161249.o6GCn6609640@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
> Andrew Dunstan wrote:
> >
> >
> > Bruce Momjian wrote:
> > > I assume SHOW TABLES would only be useful for interactive terminal
> > > sesssions, not for application code (which should use
> > > information_schema), so what non-psql interactive terminal programs are
> > > there?
> > >
> > >
> >
> > I think your assumption is questionable.
> >
> > Plenty of people use MySQL's "SHOW TABLES" in non-interactive settings
> > (for good or ill). That's why any suggestion that we should return
> > anything other than a resultset seems like a really terrible idea to me.
>
> If they are writing an application, finding the query to show all tables
> is the least of their problems. I don't see how SHOW TABLE
> significantly helps in that case, except make things 0.001% easier,
> while creating duplicate functionality in Postgres.
What would be interesting is if SHOW TABLES was psql-only, and showed
the output in multi-column format, like ls -C. That would a a new
display format and new useful functionality.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ None of us is going to be here forever. +
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2010-07-16 12:51:23 | Re: reducing NUMERIC size for 9.1 |
Previous Message | Brendan Jurd | 2010-07-16 12:44:39 | Re: reducing NUMERIC size for 9.1 |