Received: from ns.krot.org (ns.krot.org [193.212.103.165]) by postgresql.org (8.11.3/8.11.4) with SMTP id f9JJCXP59112 for ; Fri, 19 Oct 2001 15:12:33 -0400 (EDT) (envelope-from postgresql@envisity.com) Received: (qmail 13570 invoked by uid 67); 19 Oct 2001 19:10:30 -0000 Message-ID: <20011019191030.2126.qmail@ns.krot.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline MIME-Version: 1.0 From: "Aasmund Midttun Godal" To: josh@agliodbs.com Cc: pgsql-sql@postgresql.org Subject: Re: oid's in views. Date: Fri, 19 Oct 2001 19:10:30 GMT X-Mailer: Googley-Moogley In-Reply-To: from Josh Berkus on Fri, 19 Oct 2001 08:07:50 -0700 References: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by postgresql.org id f9JJKXM61136 X-Archive-Number: 200110/282 X-Sequence-Number: 5235 On Fri, 19 Oct 2001 08:07:50 -0700, "Josh Berkus" 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