<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 22/05/2014 21:39, Phil Roberts
wrote:<br>
</div>
<blockquote cite="mid:SNT153-W746D9764D7D65CB7802D9FBE3F0@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">Have started investigation moving three backends to
a new single backend and wish to retain the 'oldrecorded'
information from each.<br>
<br>
machine 1 - running myth 0.19.20060121-2 ( built from scratch -
6000+ recordings )<br>
machine 2 - running myth 0.23 fixes ( mythbuntu )<br>
machine 3 - running myth 0.25 fixes ( mythbuntu )<br>
<br>
machine 4 - new environment myth 0.27 fixes<br>
<br>
A mysqldump of oldrecorded from 0.23 and 0.25 results in
dropping the database table before inserting the records. That
is not so difficult to resolve. ( remove the drop and ALTER
instead of CREATE ) I think.<br>
</div>
</blockquote>
<br>
You could:<br>
<br>
- dump the database from m1 to file<br>
- create a new database on m4<br>
- import m1 database file onto m4<br>
- start up myth on m4 so that it upgrades the schema<br>
- dump the new m4 database to file<br>
- drop the database on m4<br>
... and repeat for m2 and m3<br>
<br>
Then you have three database files that have identical schemas
(compatible with 0.27) and how you merge them is a lot easier
(although not nice).<br>
<br>
I'm sure that someone on here will know a better myth-centric way,
but ...<br>
<br>
Nige.<br>
</body>
</html>