Comments on: mysql argh https://www.lafferty.ca/2005/10/12/mysql-argh/ Rich Lafferty's OLD blog Sun, 11 Feb 2007 18:43:01 +0000 hourly 1 https://wordpress.org/?v=5.9.2 By: Rich https://www.lafferty.ca/2005/10/12/mysql-argh/comment-page-1/#comment-2126 Fri, 14 Oct 2005 05:39:03 +0000 #comment-2126 I don’t have any reason to think that MySQL will fork InnoDB. They didn’t have the resources to buy Innobase, and similarly won’t be in a position to poach key people from them now that they’re owned by Oracle. Any development would have to come from existing or new inside resources, and there’s nothing in the GPL that makes maintaining that level of development easy. Even if people can get up to speed something has to give.

The problem is that MySQL AB is now in an awkward position for their revenue-generating products: the client libraries and support. Until now they’ve been pricing their client libraries as if they were the database, even though the database; that’s a lot harder to do when it’s clear to customers that large chunks of what they seem to be buying are owned by a competitor.

If MySQL AB is going to separate themselves from dependence on Innobase Oy it’s going to be by prioritizing BDB and working with Sleepycat. I don’t know if they’ll do that, or just hope they don’t anger their new partner; I don’t think Oracle would buy Innobase to kill MySQL, I think they bought it to put themselves in a very good bargaining position with a competitor that now needs them.

]]> By: leolo https://www.lafferty.ca/2005/10/12/mysql-argh/comment-page-1/#comment-2125 Thu, 13 Oct 2005 21:58:57 +0000 #comment-2125 InnoDB is GPL, so while Oracle might scale back any developement, it’s not going to disapear. New dev will happen at MySQL AB and in the community.

So I wouldn’t worry much.

]]> By: euqsam https://www.lafferty.ca/2005/10/12/mysql-argh/comment-page-1/#comment-2124 Thu, 13 Oct 2005 05:48:19 +0000 #comment-2124 Ooh. Tasty tip. mendel++

]]>