On Wed, Jul 22, 2009 at 11:20 AM, Indranil Das Gupta <span dir="ltr"><<a href="mailto:indradg@gmail.com">indradg@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi all,<br>
<br>
These last couple of hours, i've been trying to access different<br>
*.<a href="http://mysql.com" target="_blank">mysql.com</a> sites (for my non-Koha work). None of them responding to a<br>
http request. I'm not being a fear-monger or crystal gazer here, but<br>
I'm dependent on MySQL for several apps that i commercially support,<br>
which includes Koha.<br>
<br>
I wonder just how ready or MySQL dependent are we (Koha users) as a<br>
community, just in case, Oracle decides to stop further work on MySQL?<br>
I'm aware of efforts like Drizzle. But how are we positioned w.r.t<br>
MySQL deps and what could hypothetically could be a possible life<br>
after MySQL (if it ever comes to that)<br>
<br>
-indra</blockquote></div><br>The servers are indeed unreachable at present. I think that is unrelated to the larger question.<br><br clear="all">It doesn't matter if Oracle stops working on mysql, the open source community will still develop it. Maybe it would fork into a different project, but there is no risk of mysql "going away". <br>
<br>That being said, the best move towards DB agnosticism for Koha is to implement an abstraction layer like DBIx::Class. We are pretty far from that right now. In fact, we may be reaching a point where this kind of of work is so overdue that it is inordinately more difficult to accomplish it. All the new work is being done without it adds to the task. And no entity is yet willing to sponsor this kind of rewrite because it adds no user-visible features, yet will take literally dozens if not hundreds of manhours. <br>
<br>-- <br>Joe Atzberger<br>LibLime - Open Source Library Solutions<br>