From: | Mike Mascari <mascarm(at)mascari(dot)com> |
---|---|
To: | Gonzo Rock <GonzoRock(at)Excite(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: RE: [SQL] Database Design Question |
Date: | 2001-07-27 20:39:31 |
Message-ID: | 3B61D183.E65B27FE@mascari.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-sql |
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(at)mascari(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | omid omoomi | 2001-07-27 20:40:48 | Re: Database Design Question |
Previous Message | Oliver Elphick | 2001-07-27 20:28:57 | Re: Re: D308-E9AF-4C11 : CONFIRM from pgsql-sql (subscribe) |
From | Date | Subject | |
---|---|---|---|
Next Message | James Orr | 2001-07-27 20:51:00 | Re: Database Design Question |
Previous Message | Ryan Mahoney | 2001-07-27 20:24:32 | Re: RE: [SQL] Database Design Question |