From: Rod Taylor <rbt@rbt.ca>
To: sailesh@cs.berkeley.edu
Cc: scott.marlowe <scott.marlowe@ihs.com>
Cc: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Are we losing momentum?
Date: 24 Apr 2003 09:06:37 -0400
Message-ID: <1051189596.46146.24.camel@jester> (raw)
In-Reply-To: <bxyadeg1m3j.fsf@datafix.CS.Berkeley.EDU>
References: <Pine.LNX.4.33.0304230922450.12251-100000@css120.ihs.com>
<bxyadeg1m3j.fsf@datafix.CS.Berkeley.EDU>
On Thu, 2003-04-24 at 01:49, Sailesh Krishnamurthy wrote:
> >>>>> "scott" == scott marlowe <scott.marlowe> writes:
>
> scott> Plus the fact that the underlying pg_ tables are stable
> scott> from release to release makes it a bit awkward to upgrade
> scott> the servers they play on. Most of them have gone ahead and
> scott> created views that give them a consistent view of the parts
> scott> of the database they need.
>
> This is exactly the reason why in db2 _no_ guarantees are made
> regarding the constancy of the system catalogs (that are in the SYSIBM
> schema). Instead, the equivalent views (in the SYSCAT schema) are
> _never_ broken (whether in a point release or a new version). In fact,
> the SYSCAT views correspond to the ISO SQL standard.
The INFORMATION_SCHEMA? Out of curiousity, how do they handle DB2
extensions? Do they create new views in that schema? Do they ignore
them?
I'm going with the assumptions DB2 has extended SQL specs in some shape
or form.
--
Rod Taylor <rbt@rbt.ca>
PGP Key: http://www.rbt.ca/rbtpub.ascAttachments:
signature.asc (application/pgp-signature, 186B) download
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: rbt@rbt.ca, sailesh@cs.berkeley.edu, scott.marlowe@ihs.com, shridhar_daithankar@persistent.co.in
Subject: Re: Are we losing momentum?
In-Reply-To: <1051189596.46146.24.camel@jester>
* 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