Congratulations, you've just created the world's worst database design! Using age as a primary key is like using a sandwich as a doorstop - technically possible but fundamentally wrong. Primary keys should be unique and unchanging, but unless you've discovered the fountain of youth, your age changes every year. Plus, there are roughly 8 million 17-year-olds on Earth right now, all trying to register for your app. No wonder it's complaining! Next time, maybe try something truly unique... like I don't know... an ID?
Age As A Primary Key: What Could Possibly Go Wrong?
2 months ago
222,156 views
0 shares
database-memes, sql-memes, primary-key-memes, bad-design-memes, data-modeling-memes | ProgrammerHumor.io
More Like This
Dating A Programmer
10 months ago
191.4K views
1 shares
Why Use MVC When The Controller Can Do Everything?!
5 months ago
268.6K views
0 shares
Goodbye Lil Bro (And 4 Million Rows)
2 months ago
286.0K views
0 shares
Test Suite Setup: The Infrastructure Apocalypse
3 months ago
269.0K views
0 shares
SQL: The Clown In The Tech Stack
5 months ago
302.9K views
0 shares
Simple is hard
4 years ago
76.4K views
0 shares
Programming Books (affiliate)
Loading more content...
AI
AWS
Agile
Algorithms
Android
Apple
Bash
C++
Csharp