Received: from penelope.cokenias.org (adsl-64-170-106-93.dsl.snfc21.pacbell.net [64.170.106.93]) by postgresql.org (Postfix) with ESMTP id 06611475A83 for ; Wed, 10 Apr 2002 17:40:15 -0400 (EDT) Received: from [10.0.1.9] (cube.lan.cokenias.org [10.0.1.9]) by penelope.cokenias.org (8.11.6/8.11.6) with ESMTP id g3ALeC728512 for ; Wed, 10 Apr 2002 14:40:12 -0700 (PDT) (envelope-from lists@mtn-palace.com) Mime-Version: 1.0 X-Sender: lists@mail Message-Id: In-Reply-To: <20020319155803.G37657-100000@megazone23.bigpanda.com> References: <20020319155803.G37657-100000@megazone23.bigpanda.com> Date: Wed, 10 Apr 2002 14:40:15 -0700 To: pgsql-general@postgresql.org From: Damon Cokenias Subject: View INSERTs not returning OID in Postgres 7.2.1 Cc: <> Content-Type: text/plain; charset="us-ascii" X-Archive-Number: 200204/412 X-Sequence-Number: 23129 I recently moved from 7.1.3 to 7.2.1. In doing so, my application broke. It relies on INSERT returning the OID of the inserted row, even if the INSERT was on a view. I saw a note in the 7.2.1 notes about fixing a problem in this area, perhaps more needs to be done? Example: acropolis=# create table shad (a integer); CREATE acropolis=# create view shadview as select * from shad; CREATE acropolis=# create rule shadview_insert as on insert to shadview do instead insert into shad values (new.a); CREATE acropolis=# insert into shad values (1); INSERT 3876425 1 acropolis=# insert into shadview values (2); INSERT 0 0 acropolis=# select * from shad; a --- 1 2 (2 rows) --------------- Shouldn't the second INSERT return an OID as well? Thanks, -Damon