From: Aasmund Midttun Godal <postgresql@envisity.com>
To: josh@agliodbs.com
Cc: pgsql-sql@postgresql.org
Subject: Re: oid's in views.
Date: Fri, 19 Oct 2001 19:10:30 GMT
Message-ID: <20011019191030.2126.qmail@ns.krot.org> (raw)
In-Reply-To: <web-151072@davinci.ethosmedia.com>
References: <web-151072@davinci.ethosmedia.com>
On Fri, 19 Oct 2001 08:07:50 -0700, "Josh Berkus" <josh@agliodbs.com> wrote:
> Aasmund,
>
>
> I believe the *official* reccommendation now is that you leave the OIDs
> to the system, and create your own SERIAL values for row identification.
> There are *lots* of problems with using OIDs as an index, and you've
> just found one more!
>
> -Josh
I don't use them in indexes foreign keys etc., however they are very usefull when your application tries to edit/update individual rows, as the oid is like a universal primary key.
>
>
> ______AGLIO DATABASE SOLUTIONS___________________________
> Josh Berkus
> Complete information technology josh@agliodbs.com
> and data management solutions (415) 565-7293
> for law firms, small businesses fax 621-2533
> and non-profit organizations. San Francisco
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
Aasmund Midttun Godal
aasmund@godal.com - http://www.godal.com/
+47 40 45 20 46
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-sql@postgresql.org
Cc: postgresql@envisity.com, josh@agliodbs.com
Subject: Re: oid's in views.
In-Reply-To: <20011019191030.2126.qmail@ns.krot.org>
* 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