[mythtv-users] Database Structure

Douglas Peale Douglas_Peale at comcast.net
Thu May 20 18:36:02 UTC 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/20/2010 05:49 AM, Brent Bolin wrote:
> On Thu, May 20, 2010 at 12:38 AM, Michael T. Dean
> <mtdean at thirdcontact.com> wrote:
>> On 05/20/2010 01:20 AM, Douglas Peale wrote:
>>>
>>> On 05/19/2010 09:01 PM, DaveD wrote:
>>>
>>>>
>>>> Comcast keeps moving channels around on me.  I have to rescan and
>>>> manually update xmltv ID and channel numbers every time they move
>>>> stuff.  This time they've only moved a single channel (105, HD version
>>>> of 5) and I'd like to just update that info.  If I do a complete rescan,
>>>> I'm starting from scratch with all channels so I want to just update
>>>> that channel but I don't know how the database stores the info.  There
>>>> are lots-O-tables with lots-O-fields.
>>>>
>>>> I have a system I use for playing around and experimenting and I did a
>>>> scan on that system just to make sure that 105 was still actually
>>>> available.  It is, and the clear QAM HD channel shows up as 5_1 and
>>>> plays fine (just like it used to on my real system before they moved
>>>> it).  So now I have all the info I need to fix the broken database
>>>> exported from my test system.  I'm looking for enough information to
>>>> figure out what fields from the test database I should import into the
>>>> regular system's database to get 105 working like 5_1 from the test
>>>> system.
>>>>
>>>> Is there a comprehensive, definitive guide/document somewhere
>>>> (preferably up-to-date) that explains all the tables and fields and what
>>>> they are used for and how they interact?  What is freqid, mplexid, etc?
>>>> What's the channelscan_channel table used for?  I'd really rather learn
>>>> to "fish" (to really understand the database schema), if I can find
>>>> enough info somewhere.  I know, I can always download the source....
>>>>
>>>
>>> Since you know the frequency ID, just rescan that channel (set the start
>>> channel and end channel to that frequency ID). This may
>>> affect a few other channels on the same frequency, but fixing that up is a
>>> lot less trouble than a complete rescan. Messing with
>>> the data base directly is much more trouble, and more risky.
>>>
>>
>> Yes, and use mythtv-setup channel editor to update the xmltvid, channel
>> number, callsign, and name.
>>
>> Mike
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>>
> 
> Using Mythweb channel editor live does the same thing correct?
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> 

Mythweb is my preferred method of editing channels, especially if you have multiple sources for the same channels (much easer to
get duplicates to all be the same if you can edit them all at once).

Just don't change the channel number of the last channel viewed on a tuner, or you will have to go back to MythTV Backend Setup
to change the tuners channel to a valid number before it will work again.

BTW, hitting the "e" key while watching live TV to edit a channel is a good way to get MythTV front end to crash.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkv1gQoACgkQe5tReOauESr+qQCeIXF80rmA8RCIiHQlCoOq/4Ah
F0wAoInC+qNHcfH2zp9KBptxvVlqZV0W
=twgj
-----END PGP SIGNATURE-----


More information about the mythtv-users mailing list