Record only this showing - cache the program data

[Scott MacKenzie <larrikin@…>]

When a 'Record only this showing' schedule is created, it should be treated as a special case in that, because the 'final' schedule is known at the time it is created (ie there is no future matching between schedule and program data, it is a non-recurring rule), any program data relevant to the schedule should be cached at the time of schedule creation, and the schedule made immune from later changes to program data (especially small changes to starttime and fields normally used for matching). It should be treated very similarly to a manual schedule in terms of conflict checking/resolution. It may be appropriate to allow the user to take advantage of the current program data iff an edit of the schedule rule is being undertaken.

The current behaviour would see this type of schedule ignored where there is any discrepancy between the starttime in the schedule versus the current starttime in program data. The discrepancy in question may be as little as one minute. The problem appears on systems that take advantage of multiple guide grabbers or program data sources.

[stuartm]

Please read the TicketHowTo

Trac is not a wishlist.

Use of multiple guide sources for a single channel is an entirely unsupported configuration.