This is quite scary, I wonder how many systems I’ve been on that have had minor unnoticed data corruptions because of this. This is truely a weird thing to not fix
Probably because it's not that scary. In practice, it would generally be a non-issue.
1) mysql server restarts are rare. you'd need a delete followed by a restart to trigger this.
2) you may be using soft deletes, which wouldn't trigger this problem anyway.
3) even if an ID gets reused, it may not actually matter (application dependent.)
Still, MySQL as any other database has one job, which is keeping data safe. Any issue causing data loss or worse silent data corruption should be considered a critical bug.
I actually used it, but at the time I didn't know better. I stopped using it when the default engine was still MyISAM, I heard that InnoDB improved it and made it a real database.
Now as you mentioned MongoDB it looks like indeed is a sister DB of MySQL.
1. Written by person (people) who did not know anything about databases and learned about them while working on them.
2. Nearly exclusive choice for hip language at the time (PHP for MySQL, NodeJS for MongoDB)
3. Performed much faster than competitive database only to turn out that it was at the cost of durability
4. New engine that supposed to improve durability (WiredTiger vs InnoDB), but even then, it still is plagued by issues caused by initial bad design.
17 comments
[ 2.9 ms ] story [ 42.2 ms ] thread1) mysql server restarts are rare. you'd need a delete followed by a restart to trigger this. 2) you may be using soft deletes, which wouldn't trigger this problem anyway. 3) even if an ID gets reused, it may not actually matter (application dependent.)
MongoDB gets a lot of bad rep because of it, MySQL supposed to be on a higher standard.
Now as you mentioned MongoDB it looks like indeed is a sister DB of MySQL.
1. Written by person (people) who did not know anything about databases and learned about them while working on them.
2. Nearly exclusive choice for hip language at the time (PHP for MySQL, NodeJS for MongoDB)
3. Performed much faster than competitive database only to turn out that it was at the cost of durability
4. New engine that supposed to improve durability (WiredTiger vs InnoDB), but even then, it still is plagued by issues caused by initial bad design.
What are the claims for mongodb?
And 14 1/2 years after the first bug report the bug is fixed and: Thank you for the bug report.