Reply to thread

Message

<blockquote data-quote="grubi" data-source="post: 194427" data-attributes="member: 52476">I think the way the EPG data from the database is evaluated should be improved.Currently new EPG data retrieved from DVB or via XMLTV is always apended to the still existing entries.When EPG data is retrieved from within the application it seems to be evaluated from the beginning to the end, where the first matching entry always has priority.This leads to the problem that if you retrieve a EPG timeframe of 14 days, changes that occur to programs at a later time (for current events e.g.) are covered by the outdated preceiding entries.The solution would be to evaluate the database entries in reverse order from the end to the beginning so that the latest retrieved EPG data has priority.The phenomen I described here are from my observations on how the program behaves. I did not take a look at the sources do far.Regards,grubi.</blockquote>

[QUOTE="grubi, post: 194427, member: 52476"] I think the way the EPG data from the database is evaluated should be improved. Currently new EPG data retrieved from DVB or via XMLTV is always apended to the still existing entries. When EPG data is retrieved from within the application it seems to be evaluated from the beginning to the end, where the first matching entry always has priority. This leads to the problem that if you retrieve a EPG timeframe of 14 days, changes that occur to programs at a later time (for current events e.g.) are covered by the outdated preceiding entries. The solution would be to evaluate the database entries in reverse order from the end to the beginning so that the latest retrieved EPG data has priority. The phenomen I described here are from my observations on how the program behaves. I did not take a look at the sources do far. Regards, grubi. [/QUOTE]

Verification