[mythtv] Channel changing Bugs...

[Chris Palmer]

Matt Zimmerman wrote
> > I don't see why a chanid has to be based on a channel number.  It should
> > simply be UNIQUE.  I don't change channels based on the chanid.  I don't
> > view the program guide based on the chanid.  The database can keep things
> > organized using an AUTOINCREMENT field for the chanid.  The only
> > additional design overhead is having to query the db for the last chanid
> > just after you do an insert, so you can know the chanid to use for other
> > inserts into other tables.
> 
> The current simple method has some useful benefits.  For example, you can
> throw away and regenerate the channel table and your scheduled recordings
> are intact.  It's also easily interpreted by visual inspection.

*definitely* handy for development, but for a "working" system, those
benefits probably aren't necessary.  :)

Well... what if the files are stored with "source.channel" prefixing the
filename instead of the "chanid"?  Then you will have enough info to rebuild
the database.

The chanid might be best suited to just linking the relational tables, or 
we'd probably have source and channel fields in all the tables and not just 
chanid (I'm assuming without looking at the table structure, otherwise 
chanid wouldn't serve much purpose).

-Chris