Hudzilla.org - the homepage of Paul Hudson
Contents > Databases > Normalisation Wish List | Report Bug | About Me ]

9.8.3     Why not separate data?

This is NOT the latest copy of this book; click here for the latest version.

While normalisation does indeed eliminate data duplication and drastically cut down on the chance of operator error, it does have some side effects. For example, to properly join two tables together to give one result is harder than a normal query, and much harder to optimise. It is also a little slower, because MySQL has to read from several places at once, rather than just one table. Of course, this second downside is negated entirely by the saving in space!





<< 9.8.2 So, what is the solution here?   9.8.4 First normal form >>
Table of Contents
Want to see this stuff in print? PHP in a Nutshell takes the core topics covered here, adds in thousands of edits from the editorial team and myself, and combines them to make an unbeatable reference for PHP programmers at all levels.



My latest book has hundreds more tips on how to use PHP, Apache, and MySQL, plus Perl, Python, shell scripts, performance tuning, and more!



Top-right shadow
 
Bottom-left shadow Bottom shadow

Comments from other readers
Be the first to add a comment to this chapter!



Add comment
Please note that by posting a comment here you are committing it to the public domain. This is important so that others can make use of your code themselves, and also so that I can incorporate helpful notes directly into the main text. Comments are limited to 2000 characters in length.

If you are reporting an error in the content, please tell me directly.

Your name/email address:
Your comment:
 
Now, in order to verify that you're a real person, please answer this simple question: what is zero plus two?
The answer is:
(please write in
numbers, eg 19)


Top-right shadow
 
Bottom-left shadow Bottom shadow