I know pg_namespace has been in release for one rev, but I was
wondering if for consistency sake there was any interest or desire or
plans to change the system catalog to pg_schema.

CREATE SCHEMA [schema_name];

SET search_path = foo,pubic;

SELECT * FROM pg_namespace;

SELECT * FROM information_schema.schemata;

The four naming schemes seem a bit disjointed.  I know schemata is
spec mandated, but the others aren't frozen by anything as far as I
can tell.  If 7.3.3 is going to be around for a while, it might be
nice to setup transitional warning and 1:1 views that allow:

     CREATE SCHEMA [schema_name];

     SET schema_path = foo,public;

     SELECT * FROM pg_schema;

to work.  Just some thoughts after trying to explain the different
naming practices to someone and being unable to give a good
justification for namespaceo != schema != search_path.  Given the
feature hasn't been around that long (only 8mo), figured it might be
worth considering now vs. in 5 years when it becomes apparent that
there not semantically connected even though they all revolve around
the same concept of schemas.  -sc

-- 
Sean Chittenden


Fri, 25 Apr 2003 14:39:56 -0700
Sean Chittenden <sean@chittenden.org>
pg_namespace -> pg_schema?
Sean Chittenden <sean@chittenden.org> writes:
> I know pg_namespace has been in release for one rev, but I was
> wondering if for consistency sake there was any interest or desire or
> plans to change the system catalog to pg_schema.

No.  The choice of catalog name was deliberate: a namespace is not
necessarily identical to a schema.  In any case, I can see no value
to renaming it at this late date.

			regards, tom lane


Fri, 25 Apr 2003 18:20:54 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: pg_namespace -> pg_schema? 
Tom Lane wrote:

>Sean Chittenden <sean@chittenden.org> writes:
>  
>
>>I know pg_namespace has been in release for one rev, but I was
>>wondering if for consistency sake there was any interest or desire or
>>plans to change the system catalog to pg_schema.
>>    
>>
>
>No.  The choice of catalog name was deliberate: a namespace is not
>necessarily identical to a schema.  In any case, I can see no value
>to renaming it at this late date.
>
>			regards, tom lane
>  
>

I wonder if we should use the term NAMESPACE instead of SCHEMA in pgAdmin3.
Any suggestions?

Andreas


Wed, 30 Apr 2003 00:19:25 +0200
Andreas Pflug <Andreas.Pflug@web.de>
Re: [HACKERS] pg_namespace -> pg_schema?
It's rumoured that Andreas Pflug once said:
>>No.  The choice of catalog name was deliberate: a namespace is not
>>necessarily identical to a schema.  In any case, I can see no value to
>>renaming it at this late date.
>
> I wonder if we should use the term NAMESPACE instead of SCHEMA in
> pgAdmin3. Any suggestions?

In pgAdmin II I deliberately folowed Tom's lead and called them Namespaces
internally and Schemas externally to avoid any confusion on the issue.
Oh, and of course the main class library was already called pgSchema...

Regards, Dave.


Wed, 30 Apr 2003 09:11:15 +0100 (BST)
"Dave Page" <dpage@vale-housing.co.uk>
Re: [HACKERS] pg_namespace -> pg_schema?