[UPHPU] Database Question

[Jacob Wright]

I would like to add my two cents worth on this topic.  Database design, like
anything else, is learning the rules, knowing the benefits of each rule, and
knowing when and why to break the rules.  Generally you want to start off by
designing the database as normalized as possible.  Then you need to go
through and un-normalize things where you don't need (and are confident that
you won't in the future) the flexability.  This will provide optimal
performance and smaller queries.

Of course, as stated earlier, you need to learn what normal form is in the
first place.

I'm just all against the "that's the rules, you have to do it that way"
mantra.  It makes slow databases, bloated object-oriented code, and boring
music.  Gotta know the rules, and then how to break them. :)

Jacob Wright

On 8/14/06, Walt Haas <haas at xmission.com> wrote:
>
> Jonathan Duncan <jonathan at jkdwebmagic.com> wrote:
>
> > On Mon, 14 Aug 2006, Webot Graphics wrote:
> >
> > >> You should read up on first, second, and third level
> normalization.  If yo
> > u
> > >> plan on creating databases at all, you should do yourself the favor
> of
> > >> understanding what normalization is.
> >
> > I would also highly suggest this book:
> > Database Design for Mere Mortals
> > http://www.amazon.com/gp/product/0201752840
>
> Another good clear introductory book is "The Practical SQL Handbook"
>
> http://www.amazon.com/gp/product/0201703092
>
> -- Walt
> -------
> Walt Haas          The Web Site Doctor - Cures Sick Web Sites
> (801) 534-1262     http://thewebsitedoctor.net
>
> _______________________________________________
>
> UPHPU mailing list
> UPHPU at uphpu.org
> http://uphpu.org/mailman/listinfo/uphpu
> IRC: #uphpu on irc.freenode.net
>