{"id":2147,"date":"2010-09-30T02:24:19","date_gmt":"2010-09-29T16:24:19","guid":{"rendered":"http:\/\/www.flamingspork.com\/blog\/?p=2147"},"modified":"2010-09-30T02:24:19","modified_gmt":"2010-09-29T16:24:19","slug":"what-was-innodb","status":"publish","type":"post","link":"https:\/\/www.flamingspork.com\/blog\/2010\/09\/30\/what-was-innodb\/","title":{"rendered":"What was InnoDB+?"},"content":{"rendered":"

Yes, I said InnoDB+ with a plus sign at the end<\/a> (also see the first comment here<\/a>).<\/p>\n

Please note that this blog post is only based on public<\/strong> information. It has absolutely nothing in it<\/strong> that I only could have learned from back when I worked at Sun or MySQL AB. Everything has links or pointers to where you can find the information out on the\u00c2\u00a0Internet and all thoughts are based on stringing these things together.<\/p>\n

There was a lot of talk around the\u00c2\u00a0acquisition\u00c2\u00a0of Sun Microsystems by Oracle about MySQL (MySQL AB was bought by Sun). Some of the talk centred around Oracle and their ability to make a closed source version of MySQL with added bits that wouldn’t be released as GPL. They’ve since proved that they’re quite willing to do this to an open source project (see OpenSolaris<\/a>).<\/p>\n

Relatively recently, a bunch of history from the old InnoDB SVN trees was imported into the MySQL source tree. You can pull the revision of the SVN tree as of InnoDB Plugin 1.0.6 release by using revid:\u00ef\u00bb\u00bfsvn-v4:16c675df-0fcb-4bc9-8058-dcc011a37293:branches\/zip:6263 \u00c2\u00a0from the MySQL repository – or just use a branch I’ve put up on launchpad for it (lp:~stewart\/haildb\/innodb-1.0.6-from-svn<\/a>).<\/p>\n

The first revision from the SVN tree was created on 2005-10-27, which you may remember was not too long after Oracle acquired Innobase on the 7th of October<\/a> that year. The next two revisions were importing the 5.0 innodb code base, and then the 5.1 code base. Previous history can be found according to this blog post on Transactions on InnoDB<\/a>.<\/p>\n

According to Monty in the comment on the Pythian blog<\/a>:<\/p>\n

Oracle did work on a closed source version of InnoDB, codename InnoDB+, but they never released it, probably because our contract with them stopped them.<\/p>\n

and from Eben Moglen’s letter to the EU Commission<\/a> (via Baron Schwartz’s blog post<\/a>):<\/p>\n

Innobase could therefore have provided an enhanced version of InnoDB, like Oracle\u00e2\u20ac\u2122s current InnoDB+, under non-GPL license<\/p>\n

Most tellingly is a lot of references in the revision history to “branches\/innodb+” as well as this commit:<\/p>\n

\n

revno: 0.5.148
\nrevision-id: svn-v4:16c675df-0fcb-4bc9-8058-dcc011a37293:branches\/innodb%2B:6329
\nparent: svn-v4:16c675df-0fcb-4bc9-8058-dcc011a37293:branches\/innodb%2B:6322
\ncommitter: vasil
\ntimestamp: Thu 2009-12-17 11:00:17 +0000
\nmessage:
\nbranches\/innodb+: change name and version
\nChange name from “InnoDB Plugin” to “InnoDB+” and
\nversion from 1.0.5 to 1.0.0.<\/p>\n

So, from the revision history I’ve managed to work out that it likely was going to have the following features:<\/p>\n