<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 06/11/2013 06:38 AM, James Hogarth
wrote:<br>
</div>
<blockquote
cite="mid:CAGkb5vdj80oBpmDje6t9p1o+B4FtKGssDapFPP-EX_xwF5naXw@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=ISO-8859-1">
<p dir="ltr"> <br>
><br>
> What do administrators have to do to prevent being migrated
from mysql to mariadb on upgrades?<br>
></p>
<p dir="ltr">If you would prefer to use community-mysql rather
than follow onto MariaDB I suspect the safest thing would be
take a backup (you do that anyway right?) and just doing this
from the filesystem is probably the simplest way. </p>
<p dir="ltr">Then use a supported method to upgrade to F19 ...
Either remove mysql before this or remove mariadb after this.</p>
</blockquote>
<br>
For the first we should not be migrating users on upgrades to
another DB solution regardless if it's an fork or not of the already
installed DB and we continue to ship it, secondly if we *must* do
that ( which is it is not in this case since we are continuing to
package and ship mysql ) we should have an opt out way for
administrators to do so at upgrade time instead of having them to
backtrack all the migration steps and revert them followed by them
finally having to remove mariadb in this case an simply big fat
warning presented at the end user during the upgrade phaze which
offers him to opt out migration and continue to use MySQL... <br>
<br>
JBG<br>
</body>
</html>