From: | <operationsengineer1(at)yahoo(dot)com> |
---|---|
To: | pgsqlnovice <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: SQL Statement Help Needed |
Date: | 2005-12-06 18:29:57 |
Message-ID: | 20051206182957.32063.qmail@web33305.mail.mud.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
--- me(at)alternize(dot)com wrote:
> From: <operationsengineer1(at)yahoo(dot)com>
> > the reason for doing this is that you eliminate
> > database dead space (people that don't have faxes
> > won't store a null in the db (i think it is null)
> and
> > the db won't have to manage the null values).
>
> correct me if i'm wrong, but i don't think having a
> completely normalized
> datastructure makes always sense. if one would need
> to query an employee and
> having all phone numbers & stuff in one single view,
> you'll end up having a
> huge amount of joins. this is bound to "cost"
> performance while the "win"
> (diskspace) is relatively small.
>
> - thomas
good point. this is absolutely true...
the OP has enough information to make the best choice
for their situation.
sometimes normalization makes sense, other times it
may not.
__________________________________________
Yahoo! DSL Something to write home about.
Just $16.99/mo. or less.
dsl.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2005-12-06 18:55:49 | Re: SQL Statement Help Needed |
Previous Message | Michael Fuhr | 2005-12-06 17:16:56 | Re: Musings on Triggers |