Received: from ns.krot.org (ns.krot.org [193.212.103.165]) by postgresql.org (8.11.3/8.11.4) with SMTP id f9J33pP17797 for ; Thu, 18 Oct 2001 23:03:51 -0400 (EDT) (envelope-from postgresql@envisity.com) Received: (qmail 9542 invoked by uid 67); 19 Oct 2001 03:01:49 -0000 Message-ID: <20011019030149.23206.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: oid's in views. Date: Fri, 19 Oct 2001 03:01:49 GMT X-Mailer: Googley-Moogley Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by postgresql.org id f9J371S18412 X-Archive-Number: 200110/271 X-Sequence-Number: 5224 CREATE VIEW testview AS SELECT test.oid, tull FROM test; ERROR: Attribute 'oid' has a name conflict Name matches an existing system attribute I think this should be allowed, because if you do: CREATE VIEW testview AS SELECT tull FROM test; SELECT oid, tull FROM testview; The oid column will always be blank. The oid column can never be used for anything usefull. There are many workarounds to this problem - and I appreciate that altering this behaviour might be contradictory to some design philosophy you may have. Just my comment that's all! Aasmund Midttun Godal aasmund@godal.com - http://www.godal.com/ +47 40 45 20 46