[mythtv-users] Send EPG data between 2 backends
Josu Lazkano
josu.lazkano at gmail.com
Wed Feb 15 09:39:02 UTC 2012
2012/2/15 Raymond Wagner <raymond at wagnerrp.com>:
> On 2/14/2012 17:43, Josu Lazkano wrote:
>> 2012/2/14 Richard Morton<richard.e.morton at gmail.com>:
>>> It's in the third paragraph on the page referenced...
>>>
>>> If you do not name any tables followingdb_name or if you use the --databases
>>> or --all-databases
>>> option, entire databases are dumped.
>>>
>>> Please excuse brevity and pistakes as this email was composed on an Android
>>> smartphone.
>>>
>>> Thanks and best regards
>>> Richard Morton
>>>
>> Thanks! This works:
>>
>> mysqldump -h localhost -u mythtv -ppass mythconverg program> program.sql
>
> No it doesn't, because you still have a bunch of data in that table that
> is specific to one single backend. If you try to import that into
> another MythTV system that is not completely identical, you're just
> going to break things. You're also missing several supplementary tables
> that contain additional program information. This all goes back to the
> general idea of not manually tinkering with the database.
>
> Getting back to Karl Dietz's suggestion, there is a script on the wiki
> that will generate an xmltv data file from your recording rules, for
> re-import on different sources or different machines. I've not used it
> or looked through it, and don't know how functional it is.
>
> http://www.mythtv.org/wiki/Cross-eit.py
Thanks!
Cross-eit.py works great!
Now I have the EPG data on both backends.
Best regards.
--
Josu Lazkano
More information about the mythtv-users
mailing list