Received: from ns.krot.org (ns.krot.org [193.212.103.165]) by postgresql.org (8.11.3/8.11.4) with SMTP id f9KBHtP17692 for ; Sat, 20 Oct 2001 07:17:56 -0400 (EDT) (envelope-from aasmund@godal.com) Received: (qmail 4070 invoked by uid 67); 20 Oct 2001 11:15:48 -0000 Message-ID: <20011020111548.697.qmail@ns.krot.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline MIME-Version: 1.0 From: "Aasmund Midttun Godal" To: pgsql-sql@postgresql.org Subject: Re: oid's in views. Date: Sat, 20 Oct 2001 11:15:48 GMT X-Mailer: Googley-Moogley In-Reply-To: from Josh Berkus on Fri, 19 Oct 2001 15:38:16 -0700 References: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by postgresql.org id f9KBKdM18291 X-Archive-Number: 200110/324 X-Sequence-Number: 5277 No, many of the tables have primary keys already, serial, single key or several keys. I don't want to 'serialize' every table, because it does not make sense. Oid's however are very usefull as I can use them as a primary key on any table. Regards, Aasmund. On Fri, 19 Oct 2001 15:38:16 -0700, "Josh Berkus" wrote: > Aasmund, > > > You'd still be better off defining your own SERIAL columns and/or > primary keys and using those. Some Trigger types require referencing > the OID, but that's about it. > > -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 Aasmund Midttun Godal aasmund@godal.com - http://www.godal.com/ +47 40 45 20 46