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?
6 months ago
349,707 views
0 shares
database-memes, sql-memes, primary-key-memes, bad-design-memes, data-modeling-memes | ProgrammerHumor.io
More Like This
Only a true programmer
3 years ago
163.3K views
0 shares
Visual Studio apparently reuses the Solitaire code
4 years ago
94.4K views
0 shares
Was browsing through a client's database docs, found a suspicious looking table
3 years ago
223.9K views
0 shares
Expectation Vs Reality: The Developer's Job Trap
7 months ago
520.7K views
0 shares
Logitech C920e HD 1080p Mic-Enabled Webcam, Certified for Zoom, Microsoft Teams Compatible, TAA Compliant
Affiliate
Webcams
Logitech
Loading more content...
AI
AWS
Agile
Algorithms
Android
Apple
Bash
C++
Csharp