[{"data":1,"prerenderedAt":79},["ShallowReactive",2],{"term-n\u002Fnormalization":3,"related-n\u002Fnormalization":60},{"id":4,"title":5,"acronym":6,"body":7,"category":40,"description":41,"difficulty":42,"extension":43,"letter":44,"meta":45,"navigation":46,"path":47,"related":48,"seo":54,"sitemap":55,"stem":58,"subcategory":6,"__hash__":59},"terms\u002Fterms\u002Fn\u002Fnormalization.md","Normalization",null,{"type":8,"value":9,"toc":33},"minimark",[10,15,19,23,26,30],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 — The Vibe Check",[16,17,18],"p",{},"Normalization is the process of organizing your database to reduce data duplication. Instead of storing a user's name in every order row, you store it once in the users table and reference it with a foreign key. Less repetition, fewer update bugs.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"Normalization is the process of structuring a relational database to reduce data redundancy and improve data integrity. It follows a series of normal forms (1NF, 2NF, 3NF, BCNF, etc.). Each form progressively eliminates specific types of data anomalies. Higher normalization typically requires more JOINs to query data.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"We normalized the schema to avoid storing duplicate user data.\" \u002F \"Over-normalization can lead to painful JOINs everywhere.\"",{"title":34,"searchDepth":35,"depth":35,"links":36},"",2,[37,38,39],{"id":13,"depth":35,"text":14},{"id":21,"depth":35,"text":22},{"id":28,"depth":35,"text":29},"database","Normalization is the process of organizing your database to reduce data duplication.","intermediate","md","n",{},true,"\u002Fterms\u002Fn\u002Fnormalization",[49,50,51,52,53],"Denormalization","First Normal Form","Schema","Foreign Key","ERD",{"title":5,"description":41},{"changefreq":56,"priority":57},"weekly",0.7,"terms\u002Fn\u002Fnormalization","nihc850EVpaW-tDRf1xGQfDzB1HSMdlBJ00lrSvab3o",[61,64,68,72,76],{"title":49,"path":62,"acronym":6,"category":40,"difficulty":42,"description":63},"\u002Fterms\u002Fd\u002Fdenormalization","Denormalization is the intentional opposite of normalization — you duplicate data to make queries faster.",{"title":53,"path":65,"acronym":66,"category":40,"difficulty":42,"description":67},"\u002Fterms\u002Fe\u002Ferd","Entity Relationship Diagram","An ERD is a visual map of your database — boxes for tables, lines showing how they connect.",{"title":50,"path":69,"acronym":70,"category":40,"difficulty":42,"description":71},"\u002Fterms\u002Ff\u002Ffirst-normal-form","1NF","First Normal Form (1NF) is the most basic normalization rule: each column should hold one value, not a list.",{"title":52,"path":73,"acronym":6,"category":40,"difficulty":74,"description":75},"\u002Fterms\u002Ff\u002Fforeign-key","beginner","A foreign key is how you link two tables together. If an 'orders' table has a 'user_id' column pointing to the 'users' table, that is a foreign key.",{"title":51,"path":77,"acronym":6,"category":40,"difficulty":74,"description":78},"\u002Fterms\u002Fs\u002Fschema","A database schema is the blueprint of your database — which tables exist, what columns they have, what types they are, and how they relate to each other.",1776518297892]