SHOW TABLES
in [PgSql]
|
From: Markus Wanner on 16 Jul 2010 08:17 > I have to agree with Simon here. \d is ridiculous for the common user. +1 Regards Markus -- 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: Steve Atkins on 16 Jul 2010 11:36 On Jul 16, 2010, at 8:11 AM, Simon Riggs wrote: > On Fri, 2010-07-16 at 14:07 +0100, Thom Brown wrote: > >> 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 > > Close, but I didn't state any of those as you have them. > > I want to make it easy for newbies to get access to obvious things like > a list of tables, from *any* interactive application, wherever they > exist. There are many and various apps and not all of them work the > same. (The Windows installer ships two, for example). It would be nice > to tell people "just type SHOW TABLES" and have it be true 100% of the > time. They can remember that, or at least will try it if they can't > remember anything at all about our RDBMS. In pretty much any GUI application the expected way to see a list of tables is not going to involve typing anything anywhere. Either the list of tables is going to be shown all the time (common) or there'll be a menu or toolbar option to show them. There may not be anywhere obvious to type in a command, and if there is the output of a server-side implementation of show tables would likely be displayed like the contents of a table, rather than as names of tables - so all the metadata is going to be off. Things like the context menu for each row of the result having operations for modifying the contents of a table, rather than the operations for modifying a table. It'll offer DML operations where you'd expect, and want, DDL in other words. Cheers, Steve -- 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 11:40 On Thu, 2010-07-15 at 15:38 -0400, 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? My original thought was around the newbie experience: they connect to PostgreSQL and then.... nothing. No sensible commands work, typing "help" doesn't work, nor does typing "quit". Few simple commands they've learnt elsewhere work either. We need a way to respond sensibly to common user input. "Terminal program" is the bit of thinking that is askew there. The question is "what other non-psql interactive programs are there"? Lots. There are many tools that can access Postgres. Some are libpq programs, though there are command line versions in every environment: java, python, etc.. -- 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
From: Bruce Momjian on 16 Jul 2010 11:44 Simon Riggs wrote: > On Thu, 2010-07-15 at 15:38 -0400, 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? > > My original thought was around the newbie experience: they connect to > PostgreSQL and then.... nothing. No sensible commands work, typing > "help" doesn't work, nor does typing "quit". Few simple commands they've Well, "help" does work now, for some definition of work: $ psql test hpsql (9.1devel) Type "help" for help. test=> help You are using psql, the command-line interface to PostgreSQL. Type: \copyright for distribution terms \h for help with SQL commands \? for help with psql commands \g or terminate with semicolon to execute query \q to quit > learnt elsewhere work either. > > We need a way to respond sensibly to common user input. > > "Terminal program" is the bit of thinking that is askew there. The > question is "what other non-psql interactive programs are there"? > Lots. > > 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? -- 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: David Fetter on 16 Jul 2010 11:46
On Fri, Jul 16, 2010 at 11:44:58AM -0400, Bruce Momjian wrote: > Simon Riggs wrote: > > On Thu, 2010-07-15 at 15:38 -0400, 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? > > > > My original thought was around the newbie experience: they connect to > > PostgreSQL and then.... nothing. No sensible commands work, typing > > "help" doesn't work, nor does typing "quit". Few simple commands they've > > Well, "help" does work now, for some definition of work: > > $ psql test > hpsql (9.1devel) > Type "help" for help. > > test=> help > You are using psql, the command-line interface to PostgreSQL. > Type: \copyright for distribution terms > \h for help with SQL commands > \? for help with psql commands > \g or terminate with semicolon to execute query > \q to quit > > > learnt elsewhere work either. > > > > We need a way to respond sensibly to common user input. > > > > "Terminal program" is the bit of thinking that is askew there. The > > question is "what other non-psql interactive programs are there"? > > Lots. > > > > 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? Yes. Cheers, David. -- David Fetter <david(a)fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter(a)gmail.com iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |