[mythtv] Channel changing Bugs...

[Martin Moeller]

I'm a bit behind on my mythtv reading so I appologize if this has
already been mentioned.

Here in Denmark, on a system called KabelTV, some channels 'share
space'', e.g. Fox Kids by day, Hallmark by night. How would that work in
the source.channel variety? I would be happy to integrate these channels
into one if one can specify, per channel, starting and ending hours, but
that may be too much work for a fairly marginal problem, I guess..

/Martin.

tor, 2003-04-10 kl. 01:25 skrev 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
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at snowman.net
> http://lists.snowman.net/cgi-bin/mailman/listinfo/mythtv-dev
-- 
Martin Moeller <martin at martinm-76.dk>