Received: from sisyphus.owlscreech.com (owlscreech.com [207.174.31.35]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4VFWEE08205 for ; Thu, 31 May 2001 11:32:14 -0400 (EDT) (envelope-from brian@owlscreech.com) Received: from cooper (server01.nicklebys.com [63.229.251.51]) by sisyphus.owlscreech.com (8.9.3/8.8.7) with ESMTP id JAA16968 for ; Thu, 31 May 2001 09:32:11 -0600 Message-Id: <200105311532.JAA16968@sisyphus.owlscreech.com> Date: Thu, 31 May 2001 09:33:11 -0600 Content-Type: text/plain; format=flowed; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v388) From: Brian Powell To: pgsql-sql@postgresql.org X-Mailer: Apple Mail (2.388) Content-Transfer-Encoding: 7bit Subject: 7.1.1 Lock Problems on Views X-Archive-Number: 200105/355 X-Sequence-Number: 3196 Greetings, I am investigating whether our application will run on 7.1.1 (from 7.0.3), and our client software only accesses the database through views for security and convenience. In our client app, we lock our table before doing something to it. Fortunately, in 7.0.3, a view looked like a table and we could perform: lock v_whatever in share row exclusive mode; However, in 7.1.1, it comes back and tells me that: ERROR: LOCK TABLE: v_whatever is not a table The HUGE advantage in 7.0.3 was that we could present our db through views and the client didn't have to know. I tried to put the lock statements into the rule of each view when the rule does the actual work, such as: create rule v_whatever_insert as on insert to v_whatever do instead ( lock whatever in share row exclusive mode; insert into whatever (blah) values (new.blah); ); However, the view won't be created, it claims there is a syntax error. So, with 7.1.1, how can I create views and lock the data when modifying the table? Thanks, --Brian