[Koha-devel] Oracle nerfs MySQL, calls it MySQL classic, and charges $2, 000+ for features like InnoDB

[Galen Charlton]

Hi,

2010/11/4 Kyle Hall <kyle.m.hall at gmail.com>:
> http://www.mysql.com/products/
> I imagine this is going to impact Koha quite a bit, as Koha has been using
> InnoDB for quite a while now. Switch to Postgres?

In the short term, since MySQL and InnoDB are GPL, Oracle can't make
the current code just disappear, but obviously the long-term prospects
are not clear.  In the medium term, adding support for MariaDB could
help -- it gives us an upgrade to 5.1, is supposed to be a drop-in
replacement for MySQL, and uses a replacement for InnoDB called XtraDB
that looks like an improvement.  On the other hand, packaging is a bit
lacking at present.  Drizzle also looks interesting, but it would
require more work to remove the MySQLisms from Koha that Drizzle
doesn't use.

As far as Postgres support is concerned, I'm all for it.  Of course,
Chris' DBIx::Class RFC [1] is the current candidate for starting to
get there.  However, I would point out that a full implementation of
DBIx::Class does not guarantee that we'll also get full Postgres
support for 3.4; there is a lot of testing that would need to be done.

[1] http://wiki.koha-community.org/wiki/RFC_for_using_DBIx_Class_in_Koha

Regards,

Galen
-- 
Galen Charlton
gmcharlt at gmail.com