pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Steve Crawford <scrawford@pinpointresearch.com>
To: Heather Johnson <hjohnson@nypost.com>
Cc: pgsql-general@postgresql.org
Subject: Re: How to Prevent Certain Kinds of Joins?
Date: Tue, 22 Feb 2005 13:05:02 -0800
Message-ID: <200502221305.02629.scrawford@pinpointresearch.com> (raw)
In-Reply-To: <421B9674.4060807@nypost.com>
References: <421B8D2D.6050800@nypost.com>
	<20050222200915.GA71591@winnie.fuhr.org>
	<421B9674.4060807@nypost.com>

On Tuesday 22 February 2005 12:30 pm, Heather Johnson wrote:
> One of the tables contains personally identifiable information
> (PII) (e.g., email, first and last name, etc.). The other contains
> "click stream" data (information about where on our website users
> have gone). In order to be sensitive to users privacy, we don't
> want to ever (even accidentally) run queries that would combine PII
> and click stream data. So we're looking for ways to put "walls" up
> against combining the data. We understand that anyone with ample
> access to the database can deliberately combine the data if they
> chose to do so in blatent violation of our policies. But we want to
> set something up that would put an obstacle or two in the path of
> anyone who might accidentally run such a query.

How about separate databases? If there is absolutely no need to 
"relate" the data in two tables, I can't see much reason other, 
perhaps, than convenience of user/group management to have them both 
in the same database. This _will_ prevent joins as long as you don't 
install the contrib/dblink module.

Of course anyone with access to both pieces of data can still export 
the data and reimport it to whatever database system they want in 
order to combine the data.



view thread (7+ messages)

Message-ID: <200502221305.02629.scrawford@pinpointresearch.com>
Permalink:  ../200502221305.02629.scrawford@pinpointresearch.com/
Also on:    postgresql.org/message-id/200502221305.02629.scrawford@pinpointresearch.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: scrawford@pinpointresearch.com, hjohnson@nypost.com, pgsql-general@postgresql.org
  Subject: Re: How to Prevent Certain Kinds of Joins?
  In-Reply-To: <200502221305.02629.scrawford@pinpointresearch.com>
  References: <421B8D2D.6050800@nypost.com> <20050222200915.GA71591@winnie.fuhr.org> <421B9674.4060807@nypost.com> <200502221305.02629.scrawford@pinpointresearch.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox