Slashdot Mirror

← Back to Stories (view on slashdot.org)

Sun's Mickos Is OK With Monty's MySQL 5.1 Rant

Posted by kdawson on from the say-what-you-want dept.

narramissic writes "Back on November 29, MySQL developer Michael Widenius trashed Sun's decision to give MySQL 5.1 a 'generally available' designation in a now-infamous blog post. Widenius warned users to be 'very cautious about MySQL 5.1' because 'there are still many known and unknown fatal bugs in the new features that are still not addressed.' And now we get Sun's response. In an interview Monday, Marten Mickos, senior VP of Sun's database group, said, 'I learned over many years about the benefits and the painfulness of absolute transparency in open source. A little bit of debate never hurts. This is part of being an open-source company. ... People are free to blog about what they want.' Doubtless, this will do nothing to end the debate over whether Widenius will follow fellow MySQL co-founder David Axmark's lead and leave Sun."

5 of 155 comments (clear)

  1. Re:Uhm by philspear · · Score: 3, Interesting

    So tell us, what exactly IS yourSQL?

  2. MySQL join performance deficiency, 2 orders of mag by nluv4hs · · Score: 5, Interesting
    My subject line sounds inflammatory yet see below for hard numbers and a simple, real example. Someone please show me how to coax MySQL to perform as well as PostgreSQL for this simple query (Postgres 496 times faster). It's been over two months since I posted this problem on two very public forums, with no response from the MySQL community. Would someone please stand up for MySQL and save it from looking weak here?!
  3. Re:MySQL join performance deficiency, 2 orders of by uss_valiant · · Score: 3, Interesting

    I'm not really touching this potato, maybe you're running into some quirks / unfortunate query. Just some quick questions:
    - Why don't you have a PK / any index in the address table?
    - Did you try a different syntax (e.g. WHERE vs. JOIN ON)?
    - Did you try setting different indexes? Tried forcing a specific index?

  4. Re:To their credit by QuietLagoon · · Score: 4, Interesting
    MySQL has never been a stable database program.

    . (5 insightful???) Well thats kind of harsh.

    I've run MySQL datase servers on my websites for nearly 10 years without one problem. Tens of thousands of hits per day. No problems. MySQL is always there, and always working.

    I only can wish that my desktop Windows were one-hundreth as reliable.

  5. Re:To their credit by StuartHankins · · Score: 3, Interesting

    I'm not having any troubles, and I populate several million records each day spread across approx 100 tables without error. I've done this for several years.

    I happen to be in a situation where the host system isn't ODBC-compliant so we hosted MySQL on the same box and use custom code to get data out of it. Then I import from MySQL into MS SQL Server. It's very quick for what I do and I haven't had to spend time on maintenance and tuning really like I do MS SQL Server. No table partitioning yet, no manual placement of indexes on separate filegroups etc. Oh, and no data loss. And while it's importing / exporting the MySQL load on the server is minimal -- I'm accustomed to seeing it 90%+ idle at that time of the morning.

    Granted, I use a small portion of its features, but even things like the ability to load data and have it either replace or append as needed saves another pass per table. With my tiny maintenance window this really helps.

    YMMV though. Maybe because I stay a version behind bleeding edge (5.0/5.1) it helps?