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?
22 days ago
176,681 views
0 shares
database-memes, sql-memes, primary-key-memes, bad-design-memes, data-modeling-memes | ProgrammerHumor.io
More Like This
Were wizards!
4 years ago
63.9K views
0 shares
I’m sorry what? No hate towards python but it is not hard to learn,
2 years ago
82.1K views
0 shares
Developers Hate This One Weird Trick
7 months ago
217.3K views
0 shares
More gold from programmer.hub3
2 years ago
153.8K views
0 shares
Choose Your Fighter (And Your Future Hairline)
8 months ago
256.6K views
0 shares
The Intern's Production Database Adventure
5 months ago
257.5K views
0 shares
Loading more content...
AI
AWS
Agile
Algorithms
Android
Apple
Bash
C++
Csharp