Received: from mailout04.sul.t-online.com (mailout04.sul.t-online.com [194.25.134.18]) by hub.org (8.9.3/8.9.3) with ESMTP id WAA59459 for ; Wed, 31 May 2000 22:45:19 -0400 (EDT) (envelope-from JanWieck@t-online.de) Received: from fwd03.sul.t-online.de by mailout04.sul.t-online.com with smtp id 12xKyw-0005Oi-01; Thu, 1 Jun 2000 04:45:14 +0200 Received: from hot.jw.home (340000654369-0001@[62.224.105.162]) by fwd03.sul.t-online.de with esmtp id 12xKyn-1wWe3cC; Thu, 1 Jun 2000 04:45:05 +0200 Received: (from wieck@localhost) by hot.jw.home (8.8.5/8.8.5) id EAA21189; Thu, 1 Jun 2000 04:24:59 +0200 From: JanWieck@t-online.de (Jan Wieck) Message-Id: <200006010224.EAA21189@hot.jw.home> Subject: Re: [SQL] Re: create view security In-Reply-To: from Peter Eisentraut at "May 31, 2000 09:35:01 pm" To: Peter Eisentraut Date: Thu, 1 Jun 2000 04:24:58 +0200 (MEST) CC: "Wallingford, Ted" , "'pgsql-admin@postgresql.org'" , pgsql-sql@postgresql.orgg Reply-To: Jan Wieck X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Sender: 340000654369-0001@t-dialin.net X-Archive-Number: 200006/15 Peter Eisentraut wrote: > Wallingford, Ted writes: > > > I am using 6.3 in this case. > > I'm sorry but that is pre-historic era around here and no one really > remembers what the problems might have been back then (other than that > they were surely plenty). Upgrading might be your best bet on all fronts. You're wrong - I remember, not 100% sure, but good enough. Just two weeks ago (funny - isn't it) I made a deal with a friend, exchanging this old 486/33DLC, 8MB, 1GB portable (640x480 gray but onboard SCSI!) with a planimeter (nice mechanic tool that fit's perfectly into my sliderule collection - that friend collects sliderules too so he knows how to get me :-). That old portable was the computer, most of the rule system fixes for v6.4 where developed on. I'm pretty sure that the Rule-Owner-Needs-Perm changes where part of it. The executor is doing a permisson check of the result- and all scan relations just before starting the execution. For v6.4 (or was THAT in 6.5 - dunno exactly) I added a little flag to the rangetable entry that tells "this relation is accessed through a view and permissions are already checked". Since then, it was the rewriter that checked if the view- owner would have the permissions for all relations used by the view. Anyway, upgrading IS the best (if not the only) choice for him. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com #