[mythtv-users] Is there a lag in rescheduling after changing programid?

[Ian Evans]

On Sat, Apr 5, 2014 at 4:31 AM, Mark Perkins <perkins1724 at hotmail.com>wrote:

> On 5 Apr 2014, at 3:54 pm, "Ian Evans" <dheianevans at gmail.com> wrote:
>
> On Sat, Apr 5, 2014 at 12:45 AM, Mark Perkins <perkins1724 at hotmail.com>wrote:
>
>> I can't for the life of me remember where, but somewhere there is a
>> duplicate detection setting where you can choose to match on previously
>> recorded, current recording, or both (or equivalent wording). If it wasn't
>> updated in oldrecorded as well then you would need to make sure that your
>> duplicate detection settings included checking the recorded table (or else
>> update in oldrecorded as well). May need to check the duplicate flag in
>> both to make sure it is not set to allow re-recording (0=yes, 1=no?) as
>> well.
>>
>>
>> Just looked at the recording rule in mythweb and it's set to check for
> duplicates in "All Recordings"...so I'm confused as to why it's not
> catching it then.
>
> _______________________________________________
>
> It might be worth checking the duplicate flag on the records in both
> recorded table and oldrecorded table. Perhaps there are some smarts in the
> code that always set duplicate flag to 0 when a generic programid is found?
>
>
So in other words there's not an easy way to handle this situation without
more developer-discouraged futzing with the db. :-(

Perhaps I'll drop a line to the channel to see why they can't supply the
proper info to Tribune.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20140405/7343c429/attachment.html>