Re: Newbie question about db normalization theory: redundant keys OK?

>> Celko what do you think of 1NF, 2NF, 3NF as programming exercises? <<

A lot of it is common sense made formal. Ask yourself what are the things in your data model -- a lot of them will be physical (customers, goods, trains, cars, etc.) A lot of them will be relationships among (not always between!) entities (customer buys goods) and have a name of their own (sales). And somethings will be fuzzy, which is where things are tricky.

>> but getting a dB into 3NF form if it's in 2NF or 1NF form is a bit of work, agreed? The U of Texas example was easy to follow but in the real world I doubt it's so cut and dry. <<

The bad news is that it is a bitch to refactor a bad RDBMS design ..

>> Keep in mind I have a few days experience in this matter, but I think I'm on the right track with the above statement. <<

You're very well, grasshopper :) Received on Sat Dec 15 2007 - 01:06:44 CET