Re: oid's in views.

From: "Aasmund Midttun Godal" <postgresql(at)envisity(dot)com>
To: josh(at)agliodbs(dot)com
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: oid's in views.
Date: 2001-10-19 19:10:30
Message-ID: 20011019191030.2126.qmail@ns.krot.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Fri, 19 Oct 2001 08:07:50 -0700, "Josh Berkus" <josh(at)agliodbs(dot)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(at)agliodbs(dot)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(at)godal(dot)com - http://www.godal.com/
+47 40 45 20 46

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Joel Burton 2001-10-19 20:34:26 Re: system maintained keys
Previous Message Andre Schnabel 2001-10-19 19:05:44 Re: Diferent databases on same query...