I find it weird when my database is not well Normalized and does not follow the 5 Normalization Rules.
- First Normal Form
- Second Normal Form
- Third Normal Form
- BCNF
- Fourth Normal Form
What's the way forward? and What has worked for you?
I find it weird when my database is not well Normalized and does not follow the 5 Normalization Rules.
What's the way forward? and What has worked for you?
For further actions, you may consider blocking this person and/or reporting abuse
Just kidding, it's a personal preference. But you can change your theme, font, etc. in your settings.
The more you know. 🌈
Erin Bensinger -
Alvaro Montoro -
Chantae P. -
Thomas Bnt -
Once suspended, adusoft will not be able to comment or publish posts until their suspension is removed.
Once unsuspended, adusoft will be able to comment and publish posts again.
Once unpublished, all posts by adusoft will become hidden and only accessible to themselves.
If adusoft is not suspended, they can still re-publish their posts from their dashboard.
Once unpublished, this post will become invisible to the public and only accessible to Geofrey Aduda.
They can still re-publish the post if they are not suspended.
Thanks for keeping DEV Community 👩💻👨💻 safe. Here is what you can do to flag adusoft:
Unflagging adusoft will restore default visibility to their posts.
Top comments (3)
Most cases get covered with a 3rd normal form. Having 10 years of coding experience I never required to go beyond 3rd normal form.
Related to the title question, it indeed is a good idea to learn how relational databases work and are implemented, since they're widely used in the software development world.
If you're an experienced developer. you might not need 1NF-2NF and 3.5NF-4NF(Don't complicate things). as 3NF already covers 1..1,0..1,0..*,1..*, and *..* relationships.
As for the question. It is indeed important to use relational database to make your data organized. But I would like to do the UI first before database. We want to know what clients want by providing the basic model before implementing it in the database. I don't want to keep on rewriting the schema every time a client wants a change of mind in their product.
To be honest .. it always depends on the type of project ur working on and the number of tables you have there . If it's gonna be a huge relationnel model(more then 10 tables for example) and u have enough of association relationship well Definitely u need to stick to these rules not just because they are rules .. but it's gonna ensure that ur DB is well coherent