Slashdot Mirror

← Back to Stories (view on slashdot.org)

David Axmark Resigns From Sun

Posted by samzenpus on from the take-this-job-and-shove-it dept.

An anonymous reader writes "From Kay Arno's blog we see that David Axmark, MySQL's Co-Founder, has resigned. This comes on top of the maybe, maybe not, resignation of Monty. We saw earlier this year that Brian Aker, the Director of Architecture, has forked the server to create a web-focused database from MySQL called Drizzle. The MySQL server has been 'RC' now for a year with hundreds of bugs still listed as being active in the 5.1 version. What is going on with MySQL?"

3 of 229 comments (clear)

  1. That's the power of the open source license. by aqui · · Score: 5, Interesting

    It allows for disagreements to be resolved by disagreeing, even when there are corporations with lots of lawyers involved.

    You can still fork it. No easy corporate lock down is possible.

    --
    ----- "Profanity is the one language that all programmers understand."
  2. Drizzle? by Joe+U · · Score: 5, Interesting

    Has anyone here used Drizzle?

    I'm about to start a new web project and I get to choose the DB. I'm concerned over the lack of stored procedures though. My last big project used SP's for everything and honestly, while initial coding was a pain, in the long run it was a huge benifit.

    I need a lean and mean webDB, so, if not Drizzle, does anyone have other recommendations?

  3. Re:MySQL sucks by theantix · · Score: 5, Interesting

    "How about the "bad connection" issue where the database server due to no reason obvious to the developer will count to ten and then just refuse new connections? How about when MySQL trips over itself and locks it's own tempfile? How about the admin gui that pretends to let you change parameters but really doesn't?"

    I've developed, debugged, administered, and administered MySQL databases for nearly a decade now, and I have never seen any of those issues you complain about.

    "How about MySQLs abmyssal speed once it has to deal with larger tables?"

    The InnoDB storage engine uses clustered indexes and is actually pretty good with large tables. Combine that with the partitioned table support in MySQL 5.1 and large tables are quite manageable. I have one OLTP application with well over 300M rows, and the server runs fine even though it is on commodity hardware.

    "but there is no use in pretending like there aren't any problems ..."

    Indeed, but they weren't what you mentioned here. I am looking for better CPU utilization on multicore systems, semi-synchronous replication, parallelized replication, better foreign key performance, and better join algorithms. Many of these features are planned of course but I want them now.

    --
    501 Not Implemented