On Mon, 2008-05-05 at 11:10 +0100, Richard Heyes wrote: > Tony Marston wrote: > > "Richard Heyes" <richardh@xxxxxxxxxxx> wrote in message > > news:481ED03B.7090200@xxxxxxxxxxxxxx > >>> The database must be properly normalised otherwise it > >>> will be difficult to get at the data you need in an efficient manner. > >> Not true. If your needs are simple for example, normalisation can increase > >> the complexity of a schema, hence increasing development time needed. > >> Sometimes for example you could use something like a SET type, and search > >> for something in it using FIND_IN_SET(). > > > > I disagree. The database should ALWAYS be normalised to at least the 3rd > > normal form. Sometimes going beyond that to 4NF, 5NF or 6NF becomes too > > complex. > > Sometimes it's just a waste of time. If your site isn't that busy, and > speed isn't crucial, why waste the time using a more complicated > database structure? Hmmm, my last post should have clarified I agreed primarily with 3rd normal form. Higher levels don't usually have the same kind of payoff. Cheers, Rob. -- http://www.interjinn.com Application and Templating Framework for PHP -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
