[mythtv-users] export/import of selected MythTV data

[Stephen Worthington]

On Tue, 04 Aug 2015 20:52:33 -0600, you wrote:

>On Wednesday, August 05, 2015 12:41:24 AM Nick Morrott wrote:
>> 
>> Unless I'm missing something, I'm sure Jerome wants his oldrecorded
>> (history) and record (rules) tables backed up?
>> 
>> The recorded table is for current recordings, which he's already said are
>> not important.
>
>That's right. But now I've seen the light, and it seems no one else has 
>tried such a thing. So I tried the standard route using a VM and minus a 
>display issue after mythtv-setup a backup of the converted database looks 
>whole and coherent. So I'll create new threads for what happens as I dry-
>run the conversion while I wait for a cut-over opportunity next Monday.
>
>Aside: I don't know how important it would be to users of pre-0.24 
>databases, and how many of them are out there, but paging through the 
>script that a DB backup really is, it seems to me that someone motivated 
>and enterprising could take mythconverg_backup.pl and the schema changes 
>between releases and create a mythconverg_convert.pl or somesuch that built 
>the script to create a database "backup" that matched the schema for a 
>psrticular release. After all, it's all just text. 

The code for the database upgrading is builtin as part of the MythTV
software and works on the mysql database.  It detects the database
schema version and has the code for doing all the schema upgrades to
the current level, in sequence.  Changing it to work on the ASCII dump
of a database would be a pretty major job, and there is no particular
need for it.  It is *much* easier to modify databases using the
existing mysql tools rather than having to write your own tools that
work on dump files.