From: Sailesh Krishnamurthy <sailesh@cs.berkeley.edu>
To: Rod Taylor <rbt@rbt.ca>
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 15:12:47 -0700
Message-ID: <bxyist3k0io.fsf@datafix.CS.Berkeley.EDU> (raw)
In-Reply-To: <1051189596.46146.24.camel@jester>
References: <Pine.LNX.4.33.0304230922450.12251-100000@css120.ihs.com>
<bxyadeg1m3j.fsf@datafix.CS.Berkeley.EDU>
<1051189596.46146.24.camel@jester>
>>>>> "Rod" == Rod Taylor <rbt@rbt.ca> writes:
>> 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.
Rod> The INFORMATION_SCHEMA? Out of curiousity, how do they
Rod> handle DB2 extensions? Do they create new views in that
Rod> schema? Do they ignore them?
Yes, the INFO SCHEMA - thankfully it's long enough since I looked at
the SQL specs .. I've started forgetting terms. If I never have to
write or read any spec material again, it won't be too soon.
Why extensions, even for things like indexes that aren't in the
standard, they create views (SYSCAT.INDEXES, SYSCAT.INDEXAUTH etc.)
Rod> I'm going with the assumptions DB2 has extended SQL specs in
Rod> some shape or form.
Certainly - it's just that the meaning and number of existing columns
and rows in the syscat views are always backward compatible. That
includes support of the info schema - for the sql standard features
that db2 supports.
So if there's something new in the catalog tables that is a result of
an extension and doesn't appear as a column in the syscat views (or
the info schema) then an appropriate column may be added to the view -
provided that this doesn't break the info schema compatibility.
--
Pip-pip
Sailesh
http://www.cs.berkeley.edu/~sailesh
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: sailesh@cs.berkeley.edu, rbt@rbt.ca, scott.marlowe@ihs.com, shridhar_daithankar@persistent.co.in
Subject: Re: Are we losing momentum?
In-Reply-To: <bxyist3k0io.fsf@datafix.CS.Berkeley.EDU>
* 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