Reply to thread

Message

<blockquote data-quote="morpheus_xx" data-source="post: 1186952" data-attributes="member: 48495">My commit note contains the reference to one possible source: the grabber for tvtv.de produced such results. IIRC the main issue were &quot;overlapping programs&quot;: there was on big program over 8 hours, and then multiple small ones in the same range. The first of this smaller programs had the same start time as the &quot;surrounding&quot; program.While this could be said to be issues of the grabber or the online site providing program information, in result it lead to programs persisted that had the same start and end time. My filter exaclty prevented this case.What I didn't know was the fact that there are xmltv sources that obmit the endtime and that other logic deals with it. As the original coded didn't solve my problem, and the new code doesn't support the other way, both should be changed to a common way.If I move the check into the correction functions, the result should be the expected one. Or a simple check constraint on the Programs table that avoids &quot;start = end&quot; would be another possibility (effective but not elegant).</blockquote>

[QUOTE="morpheus_xx, post: 1186952, member: 48495"] My commit note contains the reference to one possible source: the grabber for tvtv.de produced such results. IIRC the main issue were "overlapping programs": there was on big program over 8 hours, and then multiple small ones in the same range. The first of this smaller programs had the same start time as the "surrounding" program. While this could be said to be issues of the grabber or the online site providing program information, in result it lead to programs persisted that had the same start and end time. My filter exaclty prevented this case. What I didn't know was the fact that there are xmltv sources that obmit the endtime and that other logic deals with it. As the original coded didn't solve my problem, and the new code doesn't support the other way, both should be changed to a common way. If I move the check into the correction functions, the result should be the expected one. Or a simple check constraint on the Programs table that avoids "start = end" would be another possibility (effective but not elegant). [/QUOTE]

Verification