Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f9JF7uP60927 for ; Fri, 19 Oct 2001 11:07:56 -0400 (EDT) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.4.1) with HTTP id 151072; Fri, 19 Oct 2001 08:07:50 -0700 From: "Josh Berkus" Subject: Re: oid's in views. To: "Aasmund Midttun Godal" , pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Fri, 19 Oct 2001 08:07:50 -0700 Message-ID: In-Reply-To: <20011019030149.23206.qmail@ns.krot.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_===151072====davinci.ethosmedia.com===_" X-Archive-Number: 200110/278 X-Sequence-Number: 5231 This is a multi-part MIME message --_===151072====davinci.ethosmedia.com===_ Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Aasmund, > The oid column will always be blank. The oid column can never be used > for anything usefull. 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 ______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 --_===151072====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= --_===151072====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= --_===151072====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= --_===151072====davinci.ethosmedia.com===_--