Re: Views, views, views! (long) - Mailing list pgsql-hackers

From Andrew - Supernews
Subject Re: Views, views, views! (long)
Date
Msg-id slrnd7lme7.2ep3.andrew+nonews@trinity.supernews.net
Whole thread Raw
In response to Views, views, views! (long)  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Views, views, views! (long)  ("Jim C. Nasby" <decibel@decibel.org>)
List pgsql-hackers
On 2005-05-06, Christopher Kings-Lynne <chriskl@familyhealth.com.au> wrote:
>> Hmmm ... we argued about this.  I was in favor of hiding the OIDs
>> because OIDs are not consistent after a database reload and names are.
>> I can see your point though; what do other people think?
>
> Well phpPgAdmin is unable to use the pg_tables view, for instance, 
> because we have no way of getting the table comment using the 
> information in that view...

If you look at the columns lists, you'll find that oids are exposed in
a number of places. In general, I didn't make a point of exposing them
everywhere, but I _did_ expose them in cases where I thought it likely
that querying by or for the oid in particular might be needed. (OIDs
are, after all, exposed quite a bit by the wire protocol and by libpq.)

Whether the balance is correct here is something I'm open to suggestions
about.

-- 
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services


pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: Views, views, views! (long)
Next
From: Tom Lane
Date:
Subject: Re: Views, views, views! (long)