Re: [pgsql-hackers] Re: Extending System Views: proposal for 8.1/8.2 - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: [pgsql-hackers] Re: Extending System Views: proposal for 8.1/8.2
Date
Msg-id 20050123214248.GZ67721@decibel.org
Whole thread Raw
In response to Re: [pgsql-hackers] Re: Extending System Views: proposal for 8.1/8.2  (Josh Berkus <josh@agliodbs.com>)
Responses Re: [pgsql-hackers] Re: Extending System Views: proposal for 8.1/8.2  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [pgsql-hackers] Re: Extending System Views: proposal for 8.1/8.2  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
On Sun, Jan 23, 2005 at 12:43:15PM -0800, Josh Berkus wrote:
> BTW, People, I really don't see the point in prodiving a dual list -- that is, 
> a list of OIDs in addition to the list of names provided in the columns of 
> each view.   The idea of these views is to keep the users *away* from 
> technical details like OIDs, which can and will change with the advancing 
> versions of PostgreSQL.

It's a question of if these views will also be used programatically.
ISTM that OIDs are the preffered method of refering to things in code
(in fact, aren't there some functions that only take OIDs?). If we want
to make names the cannonical way to reference things in code, then I
agree that there's not much use to OIDs.

Is the long term plan to remove OIDs entirely?
-- 
Jim C. Nasby, Database Consultant               decibel@decibel.org 
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"


pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Much Ado About COUNT(*)
Next
From: "Jim C. Nasby"
Date:
Subject: Shortcut for defining triggers