From: Peter Harvey <pharvey@codebydesign.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-hackers@postgresql.org
Subject: Re: RFD: schemas and different kinds of Postgres objects
Date: Mon, 21 Jan 2002 17:39:05 -0800
Message-ID: <02012117390500.02279@p12.codebydesign.com> (raw)
In-Reply-To: <12239.1011661590@sss.pgh.pa.us>
References: <Pine.LNX.4.30.0201211840260.687-100000@peter.localdomain>
<12239.1011661590@sss.pgh.pa.us>
FYI: Applications like Data Architect would benefit from a consistent and
complete interface to the schema. For example; I found that we had to bypass
the DD views which exist (as I recall) because they did not give us all
information we needed. So we selected stuff from the system tables directly.
Yucky. Sorry I can not recall details but thought that I would mention this
here. The MySQL 'SHOW' statements seem to work pretty well and shields us
from changes to the system tables.
Peter
> I don't buy that premise. It's true that SQL92 equates ownership of a
> schema with ownership of the objects therein, but AFAICS we have no hope
> of being forward-compatible with existing database setups (wherein there
> can be multiple tables of different ownership all in a single namespace)
> if we don't allow varying ownership within a schema. I think we can
> arrange things so that we are upward compatible with both SQL92 and
> the old way. Haven't worked out details yet though.
>
> Have to run, more later.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: pharvey@codebydesign.com, tgl@sss.pgh.pa.us, peter_e@gmx.net
Subject: Re: RFD: schemas and different kinds of Postgres objects
In-Reply-To: <02012117390500.02279@p12.codebydesign.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox