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."

Comments

Injection?

[Tetsujin]

Somehow when I put "SQL" and "injection" together, I don't like the result...

Well, except for when it involves Little Bobby Tables...

Re:Injection?

[necro2607]

Yeah, who writes these headlines? It's like, let's throw together the most fucking sensationalist possible combination of words to evoke certain responses in peoples' minds when they read this headline. Instead of just writing something constructive like "MySQL adds code from Google", it has to be some sensationalistic crap so as to make people go "OMG SQL injection?!? Sum1 haxed MySQL??" and immediately read the article. What is this, FOX News or something? :P

Hells yeah

[rsborg]

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)?

Re:Hells yeah

[Dan Berlin]

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).

Re:MySQL?

[LWATCDR]

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.

Re:MySQL?

[Frosty Piss]

Why did Google choose such a crappy database?

Clearly they know something you don't.

Transplant to Postgres?

[Doc Ruby]

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.

Re:Very Niiiice

[Chineseyes]

Why on earth would you compare MySQL with Access? I'm more of a Postgres guy myself but even Mysql deserves better than that.

Google needs to add an SQL function

[LiquidCoooled]

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

Re:MySQL?

[LurkerXXX]

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.

Good stuff coming out of google

[shmert]

For the Java coders out there, Google is also releasing google collections, which looks quite nice. There's a new interview here with the authors. It's fun stuff to poke around in, and appears to be extremely well-written code.

Once this stabilizes, I'll probably be using it. It's nice to see such a direct impact on my work from their contributions. Thanks guys!