Slashdot Mirror

← Back to Stories (view on slashdot.org)

MySQL to Get Injection of Google Code

Posted by ScuttleMonkey on from the who-to-trust-on-replication dept.

inkslinger77 writes to mention that MySQL has published their software roadmap out through 2009 and it includes an injection of code from Google. Google remains relatively secretive about how their systems work but they are one of the largest users of MySQL. Earlier this year Google signed a Contributor License Agreement which provides a framework for them to contribute code to MySQL. "The search company has done a lot of work customizing MySQL to meet its special needs, which include better database replication, and tools to monitor a high volume of database instances, Axmark said in an interview at MySQL's user conference in Paris. MySQL will include some of those capabilities in future versions of its database, probably in point upgrades to MySQL 6.0, which is scheduled for general availability in late 2008, Axmark said."

3 of 195 comments (clear)

  1. Re:MySQL? by LWATCDR · · Score: 5, Informative

    I prefer PostgreSQL but MySQL isn't crappy.

    For years MySQL offered better write a few read a lot databases than PostgreSQL. It may still offer better performance for those types of operations. That is the way most websites used MySQL. It is a good tool for some applications. Slashdot is one of them.
    Yes I think PostgreSQL is better but MySQL isn't crappy.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  2. Re:Hells yeah by Dan+Berlin · · Score: 4, Informative

    We don't distribute it, so we aren't required to submit the changes back.
    We of course, try to contribute back all the changes we possibly can.

    If you look around, you'll see we just don't publicize all the changes we contribute back (and we in fact, didn't publicize this one ourselves).

  3. Re:MySQL? by LurkerXXX · · Score: 4, Informative

    MySQL cannot enforce foreign keys constraints on MyISAM tables. It 'kinda' can on Innodb tables.

    Having them and enforcing them so they are actually useful are 2 different things.

    And if you'd bother to RTFA, you would see that MySQL is moving to away from Innodb to 'falcon'. "but some InnoDB features, like foreign key support and full-text indexing, won't be supported until MySQL 6.1.".

    So MySQL is moving away from the only table types that can actually 'kinda' enforce the use foreign keys at all.

    I think that would make you the douche.