News for hackers. Stuff that matters.
Re:An open MySQL bug receives a real Birthday cake by bcoates on Friday June 28, 2013 @03:01PM (#5959759)
I don't believe in autoincrement so I'm not up to date on the evil things you can do with it, so I'm unclear why this bug matters: All it does is change the arbitrarily chosen start value for new rows, what could that break?

The existing behavior makes more sense anyway, as it preserves 'truncate table' <=> 'restore nodata dump' equivalence better.

Re:An open MySQL bug receives a real Birthday cake by miahi on Friday June 28, 2013 @03:08PM (#5959795)
That is also a way to solve it: make it a documented change. But it looks like it was completely ignored. So happy birthday!
Re:An open MySQL bug receives a real Birthday cake by Dylan16807 on Friday June 28, 2013 @03:24PM (#5959866)
It's less that it would break anything and more that it's philosophically wrong to be outputting what's basically a historical max value field when asked not to output data.