It would be really awesome if MySQL crew could spend a few months (half a year?) working on paper-cuts: https://bugs.mysql.com/search.php?search_for=&status=Ac

It would be really awesome if MySQL crew could spend a few months (half a year?) working on paper-cuts: https://bugs.mysql.com/search.php?search_for=&status=Active&severity=&limit=10&order_by=&cmd=display&direction=ASC&os=0&phpver=&bug_age=0 https://bugs.mysql.com/search.php?search_for=&status=Active&... That's all the active bugs against MySQL. Note that this 10 year old bug isn't the oldest. This is the oldest, from March 2003: https://bugs.mysql.com/bug.php?id=199 https://bugs.mysql.com/bug.php?id=199 Note someone submitted a fix for that over a year ago (and verified under the OCA in November) but it still hasn't shipped. This is a bug that should never have taken 11 years to fix. https://bugs.mysql.com/bug.php?id=3052 https://bugs.mysql.com/bug.php?id=3052 This one is great. ROLLBACK in a stored procedure doesn't close the cursor. MySQL, for all its strengths, often feels like there is a bunch of typical geeks running the show. Lots of focus on the 'sexy' new features, not so much focus on keeping the lights on.