Received: from corvette.mascari.com (dhcp065-024-161-045.columbus.rr.com
	[65.24.161.45])
	by postgresql.org (8.11.3/8.11.1) with ESMTP id f6RKgHf52478
	for <pgsql-general@postgresql.org>;
	Fri, 27 Jul 2001 16:42:18 -0400 (EDT)
	(envelope-from mascarm@mascari.com)
Received: from mascari.com (ferrari.mascari.com [192.168.2.1])
	by corvette.mascari.com (8.9.3/8.9.3) with ESMTP id QAA17047;
	Fri, 27 Jul 2001 16:31:56 -0400
Message-ID: <3B61D183.E65B27FE@mascari.com>
Date: Fri, 27 Jul 2001 16:39:31 -0400
From: Mike Mascari <mascarm@mascari.com>
Organization: Mascari Development Inc.
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Gonzo Rock <GonzoRock@Excite.com>
CC: pgsql-general@postgresql.org
Subject: Re: RE: [SQL] Database Design Question
References: <3.0.5.32.20010727110215.00c9bac0@postoffice.pacbell.net>
	<3.0.5.32.20010727132144.009eae90@postoffice.pacbell.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200107/984
X-Sequence-Number: 13104

Gonzo Rock wrote:
> 
> OK... Fair Enough... Good Points indeed y'all.
> 
> Well... What about the problem of users trying to Query the Database??
> 
> You know... like when using Crystal Reports or something?.
> 
> SELECT * from HistoryTable
> WHERE PartID = SomeInteger
> 
> vs
> 
> SELECT * from HistoryTable
> WHERE PartNum = 12345636 AND PartRev = C
> 
> How are they supposed to know What the PartID is ??
> 
> Anyway, that I why I was considering changing... current users always have trouble peering into the database... They don't quite get it.

Depending upon the sophistication of your users, you might want to
consider constructing a number of views where the data is pre-joined
(totally denormalized). We essentially do the same thing for both the
reasons you provide as well as for security purposes (row security)
based upon the value of CURRENT_USER.

Hope that helps,

Mike Mascari
mascarm@mascari.com