Slashdot Mirror


A Tale of Two MySQL Bugs

New submitter Archie Cobbs writes "Last May I encountered a relatively obscure performance bug present in both MySQL 5.5.x and MariaDB 5.5.x (not surprising since they share the same codebase). This turned out to be a great opportunity to see whether Oracle or the MariaDB project is more responsive to bug reports. On May 31 Oracle got their bug report; within 24 hours they had confirmed the bug — pretty impressive. But since then, it's been radio silence for 3 months and counting. On July 25, MariaDB got their own copy. Within a week, a MariaDB developer had analyzed the bug and committed a patch. The resulting fix will be included in the next release, MariaDB 5.5.33."

11 of 191 comments (clear)

  1. who cares? by Anonymous Coward · · Score: 1, Insightful

    mysql is of historical curiosity. At best.

    1. Re:who cares? by Anonymous Coward · · Score: 3, Insightful

      Read the post quoted above you fucklord. It had nothing to do with how good MySQL was and everything to do with how "irrelevant" it is even though it's used on every single fucking shared hosting box ever.

      And yes, it sucks.

    2. Re:who cares? by Literaphile · · Score: 5, Insightful

      No, but it is how you tell whether something is "of historical curiosity", which obviously MySQL is not, since it's the most popular RDBMS by far.

    3. Re:who cares? by greg1104 · · Score: 3, Insightful

      You might not agree with their methodology, but I did provide a reference for my claim. You should try it some time. Betting on a hunch is not a path to successful argument.

    4. Re:who cares? by WaffleMonster · · Score: 3, Insightful

      I'd be willing to bet there are more deployments of MySQL than of all other standalone RDBMSs combined.

      I'd be willing to bet there are more deployments of SQLite than all other standalone RDBMSs combined.

  2. This is surprising why? by PhrostyMcByte · · Score: 5, Insightful

    Small projects can be about purity. Making the best possible code base you can. Especially ones where people work on it for free -- they wouldn't be working on it if they didn't deeply believe in it.

    Large corporations have different goals. The success of a changeset is not measured in how many bugs you fix or even how many features you add, but how much positive impact your paying customers and shareholders perceive.

  3. Well... by Ramirozz · · Score: 5, Insightful

    If he would have the right intention to measure response time both bug reports should have been filed at the same time... filing a seocnd one with the text saying "hoping it gets more attention than the competition" is pretty biased and provocative to the actions.

    --
    http://www.quasarcr.com/
  4. Not really a fair test by greenreaper · · Score: 5, Insightful

    The poster made a comment in the second bug saying that they hoped to get a faster response than on the MySQL bug.

  5. Re:We need more data by Darinbob · · Score: 4, Insightful

    A sample size of one is insufficient to make any meaningful conclusions.

    That sort of thinking won't get you very far in politics.

  6. Re:Translation by ultranova · · Score: 3, Insightful

    If you can take it out with no effect on the result, then why is it in there in the first place?

    Dynamic query generation? The literal might actually be a variable on the client side - say, the contents of some optional string.

    --

    Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

  7. Re:Oracle will have the patch when they buy MariaD by greg1104 · · Score: 3, Insightful

    Yup, MariaDB is playing the same copyright assignment tricks that Monty used before, so that he could leverage community work yet still sell MySQL as a business. No reason to believe he's doing anything different this time. When the FSF asks for copyright assignment, that's acceptable because they have never breached the trust of their contributors. But when Monty does it, you have to assume he's setting things up so he can cash out again.