On 05/06/05, Stuart Morgan <[EMAIL PROTECTED]> wrote: > On Sun 5 June 2005 11:41, Charlie Brej wrote: > > Ed W wrote: > > > So the table ends up looking something like this (give or take I can't > > > remember the exact syntax) > > > > > > || ID || XMLTV_ID || Chan_Name || Icon > > > || 4212 || bbc1.radiotimes.co.uk || BBC One || > > > > > > http://www.radiotimes.com/icons/bbc1.jpg > > > > > > || 3223 || ... etc ... || > > > > Can someone explain to me why we need the stream IDs in the list? When the > > tuning is done the channel names are picked up automatically anyway and the > > whole thing can be driven off those. > > Channel names do change from time to time - best example is TMF which has > undergone three changes in the last 2 months. IDs remain fairly constant but > vary region to region for some channels - which leads to your next point. > > > Just a simple question of which region you are in in order to set > > BBC1/BBC2/ITV1. > > By using the IDs we shouldn't have to ask that question - the ID tells us > which region. BUT it appears there may also be different IDs for the same > regions which means lots of duplication. > > One argument in favour of using service IDs is my setup. I have changed some > channel names, and I doubt that I am alone in that. >
A complication is that you can't trust service ids either :) We're lucky in the UK 'cos they do stay constant. TBH we probably need both with some precedence rules. I think Taylor was planing on adding an immutable field somewhere to store the service name. -- John _______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
