Received: from ns.krot.org (ns.krot.org [193.212.103.165]) by postgresql.org (8.11.3/8.11.4) with SMTP id f9MHS8P45315 for ; Mon, 22 Oct 2001 13:28:10 -0400 (EDT) (envelope-from postgresql@envisity.com) Received: (qmail 6437 invoked by uid 67); 21 Oct 2001 22:12:55 -0000 Message-ID: <20011021221255.1542.qmail@ns.krot.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline MIME-Version: 1.0 From: "Aasmund Midttun Godal" To: joel@joelburton.com Cc: josh@agliodbs.com, pgsql-sql@postgresql.org Subject: Re: oid's in views. Date: Sun, 21 Oct 2001 22:12:55 GMT X-Mailer: Googley-Moogley In-Reply-To: from Joel Burton on Sat, 20 Oct 2001 23:34:44 -0400 (EDT) References: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by postgresql.org id f9MJb9S83657 X-Archive-Number: 200110/297 X-Sequence-Number: 5250 That is what i did... Regards, Aasmund On Sat, 20 Oct 2001 23:34:44 -0400 (EDT), Joel Burton wrote: > On Sun, 21 Oct 2001, Aasmund Midttun Godal wrote: > > > > Aasmund -- > > If your problem is that you want to update VIEWs and aren't sure what the > PK for the view is, could you follow a standard like this: > > CREATE TABLE person (social_security CHAR(9), full_name TEXT); > > CREATE VIEW pers_view AS select social_security AS primkey, > social_security, > full_name); > > and know that you can always find the "primkey" field in the view as one > to use in where clauses for updates? > > HTH, > -- > > Joel BURTON | joel@joelburton.com | joelburton.com | aim: wjoelburton > Independent Knowledge Management Consultant > Aasmund Midttun Godal aasmund@godal.com - http://www.godal.com/ +47 40 45 20 46