Koha and MariaDB - lets switch and start testing
hi Folks i am just sending out an email to encourage Koha developers to switch to MariaDB for their Koha dev/testing/QA work why? its highly probable MariaDB will be the database Koha switches to when MySQL explodes, (which might be quite soon, according to some) so… lets prepare for that situation by starting to testing Koha/MariaDB now, rather than later... by using Koha on MariaDB as we do our everyday work, we are also testing Koha on MariaDB for no extra effort fyi: 6 weeks ago, i switched to MariaDB for my dev and QA work, so far - ZERO problems :)
On Sun, Nov 11, 2012 at 6:59 PM, Mason James <mtj@kohaaloha.com> wrote:
hi Folks
i am just sending out an email to encourage Koha developers to switch to MariaDB for their Koha dev/testing/QA work
I've been singing this tune for awhile and am still all for it. :-)
fyi: 6 weeks ago, i switched to MariaDB for my dev and QA work, so far - ZERO problems :)
There are a couple of gotchas as MariaDB's sql seems to be a bit stricter in some places. I'll try to remember to have a look tomorrow at my old dev repo which I ran over MariaDB for about a year. I think I have some patches for the areas I found. Nothing major, though. .... time passes .... I found them and attached them to the bug we opened for this very long ago: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5366 They may or may not apply at this point, but should at least indicate where I found issues. Kind Regards, Chris
Any sources as to the "MySQL going to explode soon" statement? I'm probably behind the times, but I hadn't heard such rumours yet? On 12 November 2012 03:12, Chris Nighswonger <cnighswonger@foundations.edu>wrote:
On Sun, Nov 11, 2012 at 6:59 PM, Mason James <mtj@kohaaloha.com> wrote:
hi Folks
i am just sending out an email to encourage Koha developers to switch to MariaDB for their Koha dev/testing/QA work
I've been singing this tune for awhile and am still all for it. :-)
fyi: 6 weeks ago, i switched to MariaDB for my dev and QA work, so far - ZERO problems :)
There are a couple of gotchas as MariaDB's sql seems to be a bit stricter in some places. I'll try to remember to have a look tomorrow at my old dev repo which I ran over MariaDB for about a year. I think I have some patches for the areas I found. Nothing major, though.
.... time passes ....
I found them and attached them to the bug we opened for this very long ago:
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5366
They may or may not apply at this point, but should at least indicate where I found issues.
Kind Regards, Chris _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Martin Renvoize Software Engineer, PTFS Europe Ltd Content Management and Library Solutions Skype: Mobile: 07725985636 http://www.ptfs-europe.com
On 12 November 2012 21:37, Martin Renvoize <martin.renvoize@ptfs-europe.com>wrote:
Any sources as to the "MySQL going to explode soon" statement? I'm probably behind the times, but I hadn't heard such rumours yet?
Oracle break everything they touch sooner or later :)
http://www.h-online.com/newsticker/news/item/Oracle-secrecy-threatens-open-M... http://openlife.cc/blogs/2012/september/simon-phipps-explains-truth-behind-m... http://blogs.computerworlduk.com/simon-says/2012/09/oracle-claims-mysql-is-s... The work with DBIx::Class and testing with MariaDB seems like a good option, worst case scenario, we have spent time making mode db independent code. Chris
Not to jump on the Oracle bashing bandwagon but the Chris' and Mason have a point. I would have to agree with Chris Cormack in that furthering the DBIx::Class work would not only help this issue but also help mitigate issues that we may run into with db dependence in the future. That all being said I am probably biased because of my work on bug 8798 (http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8798). Elliott Davis On Nov 12, 2012, at 2:49 AM, Chris Cormack <chris@bigballofwax.co.nz> wrote:
On 12 November 2012 21:37, Martin Renvoize <martin.renvoize@ptfs-europe.com> wrote: Any sources as to the "MySQL going to explode soon" statement? I'm probably behind the times, but I hadn't heard such rumours yet?
Oracle break everything they touch sooner or later :)
http://www.h-online.com/newsticker/news/item/Oracle-secrecy-threatens-open-M...
http://openlife.cc/blogs/2012/september/simon-phipps-explains-truth-behind-m...
http://blogs.computerworlduk.com/simon-says/2012/09/oracle-claims-mysql-is-s...
The work with DBIx::Class and testing with MariaDB seems like a good option, worst case scenario, we have spent time making mode db independent code.
Chris _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
On 2012-11-12, at 9:37 PM, Martin Renvoize wrote:
Any sources as to the "MySQL going to explode soon" statement? I'm probably behind the times, but I hadn't heard such rumours yet?
hmmm, i just googled that for you here's a good rumor -> https://plus.google.com/105487854388646525021/posts/1eDDV5v4iqe
On Sun, Nov 11, 2012 at 8:59 PM, Mason James <mtj@kohaaloha.com> wrote:
hi Folks
i am just sending out an email to encourage Koha developers to switch to MariaDB for their Koha dev/testing/QA work
why? its highly probable MariaDB will be the database Koha switches to when MySQL explodes, (which might be quite soon, according to some)
so… lets prepare for that situation by starting to testing Koha/MariaDB now, rather than later... by using Koha on MariaDB as we do our everyday work, we are also testing Koha on MariaDB for no extra effort
What's the compatibility level for InnoDB and what steps are needed to get the DB running in MariaDB? We are concerned about this switch proposal as introducing a new DB engine into our infrastructure won't be straight-forward. The work on getting a persistency layer providing db-agnostic code is the path we should follow. Elliot, if there's anything we can help with, just let us know! Regards To+
On Mon, Nov 12, 2012 at 8:44 AM, Tomas Cohen Arazi <tomascohen@gmail.com>wrote:
What's the compatibility level for InnoDB and what steps are needed to get the DB running in MariaDB?
MariaDB is a fork of MySQL. Other than those already noted in my initial response, I noted no issues using MariaDB as a drop-in for MySQL. I was not, however, running on a production system. Note, however, that you can install MariaDB over top of MySQL db files and it will pickup without issue, so the switch is very simple. Kind Regards, Chris
On Mon, Nov 12, 2012 at 11:03 AM, Chris Nighswonger <cnighswonger@foundations.edu> wrote:
On Mon, Nov 12, 2012 at 8:44 AM, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:
What's the compatibility level for InnoDB and what steps are needed to get the DB running in MariaDB?
MariaDB is a fork of MySQL. Other than those already noted in my initial response, I noted no issues using MariaDB as a drop-in for MySQL. I was not, however, running on a production system. Note, however, that you can install MariaDB over top of MySQL db files and it will pickup without issue, so the switch is very simple.
Thanks for your response. I know what MariaDB is, is just that I know InnoDB as is does not exist on MariaDB but a replacement (XtraDB) which I know does not implement everything InnoDB does. It doesn't mean it wouldn't implement everything we (Koha) need. Do we need to change ENGINE=InnoDB in our dumps to test? Regards To+ P.S: I'm more worried about multi-master setups and that kind of stuff.
On Mon, Nov 12, 2012 at 9:16 AM, Tomas Cohen Arazi <tomascohen@gmail.com>wrote:
Thanks for your response. I know what MariaDB is, is just that I know InnoDB as is does not exist on MariaDB but a replacement (XtraDB) which I know does not implement everything InnoDB does. It doesn't mean it wouldn't implement everything we (Koha) need. Do we need to change ENGINE=InnoDB in our dumps to test?
As I said, I did a simple drop-in replacement of MySQL with MariaDB, making only a couple of syntactical changes to SQL statements as mentioned. I did not find it necessary to change the engine type. Again, this was not on a production system. That said, I never had any problems adding, removing, editing, searching records during the time I ran MariaDB. I did not dump and re-import my dbs, though, I let MariaDB run over the DB files MySQL had created. I'm not advocating this sort of move untested, only saying that many months of working over it did not scare up any major issues from my prospective. Its been quite a while ago, so I could be forgetting something and certainly ymmv as always. Kind Regards, Chris
On 2012-11-13, at 3:16 AM, Tomas Cohen Arazi wrote:
On Mon, Nov 12, 2012 at 11:03 AM, Chris Nighswonger <cnighswonger@foundations.edu> wrote:
On Mon, Nov 12, 2012 at 8:44 AM, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:
What's the compatibility level for InnoDB
xtradb it a fork of innodb, so its compatibility level is 100% with innodb
and what steps are needed to get the DB running in MariaDB?
no steps are needed, it just works
I know what MariaDB is, is just that I know InnoDB as is does not exist on MariaDB but a replacement (XtraDB) which I know does not implement everything InnoDB does.
no, xtradb *does* implement everything InnoDB does, with some extra enhancements
Do we need to change ENGINE=InnoDB in our dumps to test?
nope, no changes are needed :)
On 2012-11-13, at 3:27 PM, Mason James wrote:
On 2012-11-13, at 3:16 AM, Tomas Cohen Arazi wrote:
On Mon, Nov 12, 2012 at 11:03 AM, Chris Nighswonger <cnighswonger@foundations.edu> wrote:
On Mon, Nov 12, 2012 at 8:44 AM, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:
What's the compatibility level for InnoDB
xtradb it a fork of innodb, so its compatibility level is 100% with innodb
oops, heres some urls on xtradb, too... http://kb.askmonty.org/en/about-xtradb/ http://www.percona.com/docs/wiki/percona-xtradb http://www.mysqlperformanceblog.com/2009/04/28/xtradb-storage-engine-release... http://www.mysqlperformanceblog.com/2008/12/16/announcing-percona-xtradb-sto... http://www.linux-mag.com/id/7356/ http://stackoverflow.com/questions/12037363/xtradb-vs-innodb
participants (6)
-
Chris Cormack -
Chris Nighswonger -
Martin Renvoize -
Mason James -
Tomas Cohen Arazi -
Travis Elliott Davis