Re: SHOW TABLES - Mailing list pgsql-hackers

From Thom Brown
Subject Re: SHOW TABLES
Date
Msg-id AANLkTim-7_V73IHjCfr4bzSSQmuxQ_IQY_GcpICp2IZm@mail.gmail.com
Whole thread Raw
In response to Re: SHOW TABLES  (Bruce Momjian <bruce@momjian.us>)
Responses Re: SHOW TABLES
List pgsql-hackers
On 16 July 2010 13:49, Bruce Momjian <bruce@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


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: SHOW TABLES
Next
From: Brendan Jurd
Date:
Subject: Re: reducing NUMERIC size for 9.1