Received: from postgresql.org.org (webmail.postgresql.org [216.126.85.28]) by postgresql.org (8.11.3/8.11.1) with SMTP id f55JQFE59384 for ; Tue, 5 Jun 2001 15:26:15 -0400 (EDT) (envelope-from pgsql-sql-owner@postgresql.org) Received: from sisyphus.owlscreech.com (owlscreech.com [207.174.31.35]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4VFC1E98056 for ; Thu, 31 May 2001 11:12:01 -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 JAA16880 for ; Thu, 31 May 2001 09:11:54 -0600 Message-Id: <200105311511.JAA16880@sisyphus.owlscreech.com> Date: Thu, 31 May 2001 09:12:54 -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 LOCK TABLE changes X-Archive-Number: 200106/42 X-Sequence-Number: 3249 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. So, in 7.1.1, do I need to move the LOCK TABLE statements from the client software and into the rules of the views? Thanks, --Brian