SHOW TABLES
in [PgSql]
|
From: Tom Lane on 15 Jul 2010 11:05 Simon Riggs <simon(a)2ndQuadrant.com> writes: > The biggest turn off that most people experience when using PostgreSQL > is that psql does not support memorable commands. > I would like to implement the following commands as SQL, allowing them > to be used from any interface. > SHOW TABLES > SHOW COLUMNS > SHOW DATABASES This has been discussed before, and rejected before. Please see archives. regards, tom lane -- 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 15 Jul 2010 11:20 On Thu, 2010-07-15 at 11:05 -0400, Tom Lane wrote: > Simon Riggs <simon(a)2ndQuadrant.com> writes: > > The biggest turn off that most people experience when using PostgreSQL > > is that psql does not support memorable commands. > > > I would like to implement the following commands as SQL, allowing them > > to be used from any interface. > > > SHOW TABLES > > SHOW COLUMNS > > SHOW DATABASES > > This has been discussed before, and rejected before. Please see > archives. Many years ago. I think it's worth revisiting now in light of the number of people now joining the PostgreSQL community and the greater prevalence other ways of doing it. The world has changed, we have not. I'm not proposing any change in function, just a simpler syntax to allow the above information to be available, for newbies. Just for the record, I've never ever met anyone that said "Oh, this \d syntax makes so much sense. I'm a real convert to Postgres now you've shown me this". The reaction is always the opposite one; always negative. Which detracts from our efforts elsewhere. -- 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: Thom Brown on 15 Jul 2010 11:30 On 15 July 2010 16:20, Simon Riggs <simon(a)2ndquadrant.com> wrote: > On Thu, 2010-07-15 at 11:05 -0400, Tom Lane wrote: >> Simon Riggs <simon(a)2ndQuadrant.com> writes: >> > The biggest turn off that most people experience when using PostgreSQL >> > is that psql does not support memorable commands. >> >> > I would like to implement the following commands as SQL, allowing them >> > to be used from any interface. >> >> > SHOW TABLES >> > SHOW COLUMNS >> > SHOW DATABASES >> >> This has been discussed before, and rejected before. �Please see >> archives. > > Many years ago. I think it's worth revisiting now in light of the number > of people now joining the PostgreSQL community and the greater > prevalence other ways of doing it. The world has changed, we have not. > > I'm not proposing any change in function, just a simpler syntax to allow > the above information to be available, for newbies. > > Just for the record, I've never ever met anyone that said "Oh, this \d > syntax makes so much sense. I'm a real convert to Postgres now you've > shown me this". The reaction is always the opposite one; always > negative. Which detracts from our efforts elsewhere. > > -- Looks like the last time this was discussed, there wasn't any clear conclusion. Someone created a patch and it's still on the TODO list: http://archives.postgresql.org/pgsql-hackers/2010-01/msg01845.php 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: =?iso-8859-1?Q?Hans-J=FCrgen_Sch=F6nig?= on 15 Jul 2010 11:35 On Jul 15, 2010, at 5:20 PM, Simon Riggs wrote: > On Thu, 2010-07-15 at 11:05 -0400, Tom Lane wrote: >> Simon Riggs <simon(a)2ndQuadrant.com> writes: >>> The biggest turn off that most people experience when using PostgreSQL >>> is that psql does not support memorable commands. >> >>> I would like to implement the following commands as SQL, allowing them >>> to be used from any interface. >> >>> SHOW TABLES >>> SHOW COLUMNS >>> SHOW DATABASES >> >> This has been discussed before, and rejected before. Please see >> archives. > > Many years ago. I think it's worth revisiting now in light of the number > of people now joining the PostgreSQL community and the greater > prevalence other ways of doing it. The world has changed, we have not. > > I'm not proposing any change in function, just a simpler syntax to allow > the above information to be available, for newbies. > > Just for the record, I've never ever met anyone that said "Oh, this \d > syntax makes so much sense. I'm a real convert to Postgres now you've > shown me this". The reaction is always the opposite one; always > negative. Which detracts from our efforts elsewhere. > > -- > Simon Riggs www.2ndQuadrant.com > PostgreSQL Development, 24x7 Support, Training and Services > simon is absolutely right here. we should not mind being a little more user friendly in this area. many people are simply used to this kind of stuff. remember when you rejected something the last time (not necessarily software). was ist because you could not make it work in 2 min or was it because you did not like something else? do you reject buying a car because of a non obvious screw in the engine or because "it somehow does not feel right"? simon made an important point and i can simply agree - regardless of whether it has been discussed before or not. if you die a beautiful death you are still dead after all. regards, hans -- Cybertec Sch�nig & Sch�nig GmbH Gr�hrm�hlgasse 26 A-2700 Wiener Neustadt Web: http://www.postgresql-support.de -- 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: Magnus Hagander on 15 Jul 2010 11:38
On Thu, Jul 15, 2010 at 17:30, Thom Brown <thombrown(a)gmail.com> wrote: > On 15 July 2010 16:20, Simon Riggs <simon(a)2ndquadrant.com> wrote: >> On Thu, 2010-07-15 at 11:05 -0400, Tom Lane wrote: >>> Simon Riggs <simon(a)2ndQuadrant.com> writes: >>> > The biggest turn off that most people experience when using PostgreSQL >>> > is that psql does not support memorable commands. >>> >>> > I would like to implement the following commands as SQL, allowing them >>> > to be used from any interface. >>> >>> > SHOW TABLES >>> > SHOW COLUMNS >>> > SHOW DATABASES >>> >>> This has been discussed before, and rejected before. �Please see >>> archives. >> >> Many years ago. I think it's worth revisiting now in light of the number >> of people now joining the PostgreSQL community and the greater >> prevalence other ways of doing it. The world has changed, we have not. >> >> I'm not proposing any change in function, just a simpler syntax to allow >> the above information to be available, for newbies. >> >> Just for the record, I've never ever met anyone that said "Oh, this \d >> syntax makes so much sense. I'm a real convert to Postgres now you've >> shown me this". The reaction is always the opposite one; always >> negative. Which detracts from our efforts elsewhere. >> >> -- > > Looks like the last time this was discussed, there wasn't any clear > conclusion. �Someone created a patch and it's still on the TODO list: > http://archives.postgresql.org/pgsql-hackers/2010-01/msg01845.php That one is about: a) doing it in psql., not the backend b) not actually implementing the command, but implementing hints for the user telling them which is the correct command Is there an actual common use-case for having these commands available for *non-psql* interfaces? -- �Magnus Hagander �Me: http://www.hagander.net/ �Work: http://www.redpill-linpro.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |