- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or register to comment.
Well I just got a great idea for next time I need to change a password.
When you pick the wrong column for your primary key.
Incredibly exclusive userbase, less than 100 users ever at any one time.
If I encountered a system that badly designed, I would check to see if it takes non-integer ages and maybe get in that way.
Why stop there? How about a lil’ white hat hacking with SQL injection :)
bob’; DROP TABLE users;
Failing that, there’s also unreasonably large numbers and negative numbers.
What happens when a user grows a year older?
Every other user will also have grown a year older, so it will be fine.
Not at the same time!
We will have to synchronize everyone’s birthday, yes.
Luckily, 40% of our users were born on January 1, anyway.
thatsthejoke.gif
I think, anyway.
A newborn user can register?
Enter NaN. Or else your age is just a number.
17.1
…and don’t forget the matches…
