Message-ID: <001201c30858$16111b70$65c8a8c0@10ww.steffann.nl>
From: "Sander Steffann" <sander@steffann.nl>
To: "PostgreSQL Hackers" <pgsql-hackers@postgresql.org>
References: <Pine.LNX.4.33.0304211417350.5883-100000@css120.ihs.com>
	<1050961628.382.4.camel@tokyo>
Subject: Re: Are we losing momentum?
Date: Tue, 22 Apr 2003 00:48:10 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

Hi,

> On Mon, 2003-04-21 at 16:26, scott.marlowe wrote:
> > Yet there is no equivalent materialized view that puts the data together
> > for the user.  I don't know about you, but show table tablename is a bit
> > easier to grasp for beginners than the above sequence of SQL statements.
>
> Granted -- but I don't think that replacing or augmenting the system
> catalogs with a set of SHOW commands is a good idea (which is what you
> suggested originally). IMHO enhancing the system catalogs by adding
> views that encapsulate more of the \ command functionality into the
> backend is a good idea, and one that should be implemented eventually.
> AFAIK that's been the consensus for some time...

I think the SHOW commands won't be neccesary when there are views to use.
There is already a good SQL command to get data/information from the
databaseserver: SELECT. Adding SHOW commands to the backend that essentially
do a SELECT on a system view are a bad thing IMHO. The user can just as easy
do a SELECT on the view himself.

All just IMHO ofcourse :)
Sander.