[mythtv-users] Database Migration

Bob Weber rjweber at ieee.org
Tue Jul 19 17:55:39 EDT 2005

On Tuesday 19 July 2005 07:30 am, Christian Hack wrote:
> > -----Original Message-----
> > From: mythtv-users-bounces at mythtv.org
> > [mailto:mythtv-users-bounces at mythtv.org] On Behalf Of Ben Curtis
> >
> > So I'm running RedHat 9 w/ Myth 0.16.  I'm building up a new
> > Fedora Core 4
> > box with Myth 0.18.  I'd like to rebuild my database from
> > scratch (there
> > are a couple of issues in my current DB with channels),
> > however, I want to
> > move over my recordings, scheduled recordings, and previous recording
> > listings (so I won't start recording shows I've already recorded).
> >
> > Can I just use mysqldump to create insert statements for the
> > oldrecorded,
> > recorded, and record tables, or do I need more data than that?
> Basically all here:
> http://www.mythtv.org/docs/mythtv-HOWTO-22.html#ss22.7
> Do the dump of old DB and move the files (if necessary). Import the dump
> into the new DB

I'd be curious if this works for you. I just did this myself, and ran into a 
snag. After following the howto and getting a restore.sql file, I couldn't 
import it because the # of rows didn't match. Some investigation showed that 
the "record" table has a new field called "parentid" in 0.18.1.

Here's what I did. Instead of appending each grep result into the same 
restore.sql file, I put each one in its own file and imported them 
individually. "record" is the only table that had a problem, so I opened that 
up in an editor and added the new field to each row (the last field, setting 
it to its default 0). Then, I could import the record table.

There's probably a better way to do this, but this worked for me. 

More information about the mythtv-users mailing list