X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id B52A48B9CA0; Tue, 22 Feb 2005 21:05:33 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 12364-03; Tue, 22 Feb 2005 21:05:30 +0000 (GMT) Received: from nypost.com (ms1.nypost.com [206.15.109.53]) by svr1.postgresql.org (Postfix) with ESMTP id B5DAF8B9BB9; Tue, 22 Feb 2005 21:05:30 +0000 (GMT) Received: from ([10.238.16.157]) by ms1.nypost.com with ESMTP id 4220067.3563397; Tue, 22 Feb 2005 16:04:59 -0500 Message-ID: <421B9E75.9050304@nypost.com> Date: Tue, 22 Feb 2005 16:04:53 -0500 From: Heather Johnson User-Agent: Mozilla Thunderbird 0.8 (X11/20041018) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Marlowe Cc: Michael Fuhr , pgsql-admin@postgresql.org, pgsql-general@postgresql.org Subject: Re: [GENERAL] How to Prevent Certain Kinds of Joins? References: <421B8D2D.6050800@nypost.com> <20050222200915.GA71591@winnie.fuhr.org> <421B9674.4060807@nypost.com> <1109105459.30529.119.camel@state.g2switchworks.com> In-Reply-To: <1109105459.30529.119.camel@state.g2switchworks.com> X-Enigmail-Version: 0.86.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.234 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE X-Spam-Level: X-Archive-Number: 200502/237 X-Sequence-Number: 16405 Scott Marlowe wrote: > Why not change the keys that currently connect them to something > different (i.e. random noise) and make a NEW table that could join them > with those random keys that is restriced access wise to only the chosen > few. This might work rather nicely. It would enable us to restrict direct access to only a single table---a table with no purpose other than to faciliate a join of these two other tables. And staff that needs direct access to the original tables can continue to have it. > Or do you need to actually ever re-reference the two datasets? If not, > then just lose the connecting data when you insert the rows. Yes, unfortunately we do need to re-reference them. But I think the idea above will work out pretty well. Thank you for your help! Heather