MySQL to Get Injection of Google Code
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."
Somehow when I put "SQL" and "injection" together, I don't like the result...
Well, except for when it involves Little Bobby Tables...
Bow-ties are cool.
Eat that, Oracle.
Seriously the database layer is being commoditized, and MySQL and PostgreSQL are leading the way.
My only question, was Google required to disclose these changes, or are they just doing the right thing (again)?
Make sure everyone's vote counts: Verified Voting
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.
I prefer Postgres to MySQL. I wonder whether these MySQL revisions will be generic enough to use to improve Postgres.
I also wish these two databases interoperated more. I'd like to use a MySQL proxy to my Postgres server, so apps depending on MySQL could still work, but use Postgres to actually process the data (or just serve as a master DB for replication). Porting apps between DBs, and huge projects to join across different apps' tables in different types of DB servers should be ancient history. Mixed DB-type clusters might not be high performance, but they'd get the iterative development started, after which performance could be just an optimization, which is the right way to do it anyway.
--
make install -not war
They need to add a GOOGLE function to allow queries to be searched nicer.
SELECT * FROM articles WHERE GOOGLE('boobies');
something similar might be available but it is a PITA to list the fields to search and specify the operators etc
liqbase