[mythtv-users] Importing recordings from 18.x into 20.x, lessons learned

[Michael T. Dean]

On 10/17/06 18:52, Ackster wrote:

>I took a dump of my old db, and yanked out just the "recorded" table.
>
># grep "INSERT INTO \`recorded\`" dbbackup.sql > recorded.sql
>  
>
...

>Later I tried testing out the MythArchive plugin, and that also failed 
>to work on my old recordings, but it gave some insight into just what 
>was happening:  BOTH MythWeb and MythArchive are reading a column that 
>didn't existing in my old db, namely:
>
>    progstart 
>
>Since they didn't exist, the default gets set to "0000-00-00 00:00:00".
>
You can't do a "partial restore" ( 
http://mythtv.org/docs/mythtv-HOWTO-23.html#ss23.7 ) of a 0.18 database 
into a 0.20 database schema.  You can either:

    a) upgrade the 0.18 database in place, then export, then drop the 
database, then create a new 0.20 database, then do a "partial restore" 
of the 0.20 export into the 0.20 database

or

    b) export the 0.18 database, drop the 0.18 database, create a new 
0.18 database, do a "partial restore" of the 0.18 database into the 0.18 
database, then upgrade the new 0.18 database in place.

progstart is not the only data you're missing.  The basename is one much 
more important one...  There are probably others.

I recommend you drop your current database, use the /entire/ export of 
the 0.18 database to re-create the 0.18 database ( 
http://mythtv.org/docs/mythtv-HOWTO-23.html#ss23.5 ), start and exit 
mythtv-setup (to upgrade the 0.18 database in place), and continue with 
the steps in a above.  Any new recordings (from between the time you 
exported the 0.18 database and when you fix the broken database) can be 
imported with myth.rebuilddatabase.pl.

Mike