News for hackers. Stuff that matters.
Re:MySql fixes autoincrement bug after 14 years of users com... by kanwisher on Saturday October 07, 2017 @06:16PM (#15425990)
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
Re:MySql fixes autoincrement bug after 14 years of users com... by icedchai on Saturday October 07, 2017 @09:06PM (#15426507)
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.)

Re:MySql fixes autoincrement bug after 14 years of users com... by takeda on Saturday October 07, 2017 @09:32PM (#15426575)
According to the comments it actually is a huge issue and multiple people got their data corrupted.
Re:MySql fixes autoincrement bug after 14 years of users com... by icedchai on Saturday October 07, 2017 @09:38PM (#15426594)
I've looked at the comments and disagree. For a 15 year old bug, there is actually not that much discussion.
Re:MySql fixes autoincrement bug after 14 years of users com... by takeda on Sunday October 08, 2017 @12:46PM (#15428889)
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.
Re:MySql fixes autoincrement bug after 14 years of users com... by noncoml on Sunday October 08, 2017 @04:46PM (#15429920)
There is no data loss caused directly by this bug.
Re:MySql fixes autoincrement bug after 14 years of users com... by takeda on Monday October 09, 2017 @12:32PM (#15435270)
Indirect data loss is still a data loss.

MongoDB gets a lot of bad rep because of it, MySQL supposed to be on a higher standard.

Re:MySql fixes autoincrement bug after 14 years of users com... by icedchai on Monday October 09, 2017 @07:08PM (#15438158)
I'm guessing you didn't use MySQL in the late 90's or early 2000's? It was basically the Mongo of its day, before InnoDB and strict SQL mode..
Re:MySql fixes autoincrement bug after 14 years of users com... by takeda on Tuesday October 10, 2017 @11:54AM (#15442807)
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.

Re:MySql fixes autoincrement bug after 14 years of users com... by noncoml on Tuesday October 10, 2017 @06:22AM (#15440672)
> MongoDB gets a lot of bad rep because of it

What are the claims for mongodb?