The hardest part of relational database design is not using SQL. The syntax for creating tables, defining keys, and writing joins can be learnt and mastered over time. The difficult part is to develop the thinking that comes before any code gets written, and answering questions about the design of the database.
Which pieces of information deserve their own table?
How should tables reference each other?
How much redundancy is too much?
These are design decisions, and getting them right means our data stays consistent, our queries stay fast, and changes are painless. Getting them wrong means spending months patching problems that were baked into the structure from day one.
In this article, we cover the core concepts that inform those decisions. We’ll look at tables, keys, relationships, normalization, and joins, with each concept building on the last.
[ad_2]
Source link
More on guide to relational database design
Stay tuned for updates on guide to relational database design as the story develops. Related: Host custom HTML applications inside Datasette.
Frequently Asked Questions
Not using SQL. The syntax for creating tables, defining keys and writing joins can be learned over time. The difficult part is the thinking that comes before any code: which pieces of information deserve their own table, how tables should reference each other, and how much redundancy is too much.
The article covers the core concepts that inform design decisions: tables, keys, relationships, normalization and joins, with each concept building on the last.
Getting them right means data stays consistent, queries stay fast, and changes are painless. Getting them wrong means spending months patching problems that were baked into the structure from day one.
