SHOW TABLES
in [PgSql]
|
From: Thom Brown on 16 Jul 2010 09:07 On 16 July 2010 13:49, Bruce Momjian <bruce(a)momjian.us> wrote: > 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. > > -- The problem is people are stating different requirements. - to make it easy for new users of psql - to simplify fetching basic database information from any client application - to ease transition between MySQL and PostgreSQL The outcome would depend on what's needed. Like providing a pg_user_tables view for people to select from, using LIST TABLES as a more meaningful alternative to SHOW TABLES, providing hints for MySQL users using psql... etc. Thom -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Pavel Stehule on 16 Jul 2010 09:06 2010/7/16 Bruce Momjian <bruce(a)momjian.us>: > 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. I am thinking same too. Maybe somebody will be happy, bacause they can to write SHOW TABLES, but they will be unsatisfied when will try to write SHOW TABLES WHERE ... so only full support of MySQL syntax has sense. Some only text version of SHOW TABLES command isn't sense for me - it can do only more problems with incompatibility. Still I thinking about top level hook - so these and similar commands can be implemented inside external modules. I have a different opinion on DESCRIBE command. This really can help. But it must not be a command. "describe" function is enought - select describe(oid); select describe_table(name); .... Regards Pavel Stehule > > -- > Bruce Momjian <bruce(a)momjian.us> http://momjian.us > EnterpriseDB http://enterprisedb.com > > + None of us is going to be here forever. + > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers > -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: "David E. Wheeler" on 16 Jul 2010 12:13 On Jul 16, 2010, at 9:09 AM, David Fetter wrote: >> Clarification, do enough people use non-psql command line tools to >> warrant putting this in the backend? > > Yes. Such backend stuff is in every RDBMS except ours. I admit that I had to do a *lot* of work to write the schema-testing functions for pgTAP. Getting information about functions is especially hairy (I poached a view from newsysviews to get what I needed). I'd love a cleaner way to get at this information. Best, David -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Bruce Momjian on 16 Jul 2010 12:16 David Fetter wrote: > On Fri, Jul 16, 2010 at 12:04:01PM -0400, Bruce Momjian wrote: > > Marc G. Fournier wrote: > > > On Fri, 16 Jul 2010, Bruce Momjian wrote: > > > > > > >> There are many tools that can access Postgres. Some are libpq programs, > > > >> though there are command line versions in every environment: java, > > > >> python, etc.. > > > > > > > > Yeah, but do enough people use them to warrant putting this in the > > > > backend? > > > > > > I may have lost the gist of this question, but ... how can they use them > > > if they don't exist? > > > > Clarification, do enough people use non-psql command line tools to > > warrant putting this in the backend? > > Yes. Such backend stuff is in every RDBMS except ours. Really? What are the other syntaxes? -- Bruce Momjian <bruce(a)momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + None of us is going to be here forever. + -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Simon Riggs on 16 Jul 2010 12:24
On Fri, 2010-07-16 at 12:16 -0400, Bruce Momjian wrote: > Really? What are the other syntaxes? SHOW TABLES -- Simon Riggs www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Training and Services -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |