aboutsummaryrefslogtreecommitdiff
path: root/blog
diff options
context:
space:
mode:
authoralex <alex@pdp7.net>2026-09-15 21:49:12 +0200
committeralex <alex@pdp7.net>2026-09-15 21:49:12 +0200
commitbb2706e6ce991afa231289c48f5ab8fcaebcc959 (patch)
tree962a86cd1bb0548194a5fa0884e7613013b479fc /blog
parent5f1454bceb3303dabffc50661afd6cf810aa75bf (diff)
Add some random notesmaster
Diffstat (limited to 'blog')
-rw-r--r--blog/content/notes/tech/about-relational-databases.gmi12
1 files changed, 12 insertions, 0 deletions
diff --git a/blog/content/notes/tech/about-relational-databases.gmi b/blog/content/notes/tech/about-relational-databases.gmi
index d08071ac..1760f0b3 100644
--- a/blog/content/notes/tech/about-relational-databases.gmi
+++ b/blog/content/notes/tech/about-relational-databases.gmi
@@ -25,3 +25,15 @@ Many computer languages have similar concepts:
* PHP arrays
Relations are a natural concept, so although non-relational data systems exist, most data can be stored as relations.
+
+## Random notes
+
+### About schema design
+
+* Only denormalize when provably forced to.
+* If implementing business logic requires complex queries, then the schema might not be optimal.
+* Normalization is not always obvious. It might look redundant to include the product unit price in the line item of an order, because the database already stores the product price, but you need to record the price at the time of the order, which might not be permanent.
+
+### Others
+
+=> real-time-relations Real-time relations describes a simpler relational database for real-time software.