[mythtv] Ticket #6438: maxEpisodes is not respected with back-to-back recordings

[Shane]

On Sat, Apr 11, 2009 at 12:38 PM, David Engel <david at istwok.net> wrote:
> On Fri, Apr 10, 2009 at 02:51:26PM -0400, Shane wrote:
>> I guess the remaining question is how does that effect the "Forget
>> Previous" case
>> mentioned in the [15808] changelog.
>>
>> Quoting Mr. Pinkham's changelog from [15808]:
>>
>> Add a menu option to allow the user to tell Myth to forget that it recorded a
>> particular recording so that it can be rerecorded even if it is a duplicate.
>>
>> The 'forgotten' program also no longer counts in the maxepisodes count for
>> the scheduled recording so that it may be rerecorded.
>>
>> This is useful when you have a bad recording of a program and want to give
>> Myth a chance to record a new copy without having to delete the old one first.
>>
>> End quote.
>>
>>
>> So, if the "AND duplicate <> 0" clause is dropped and the user hits
>> "Forget Previous",
>> the forgotten program will be marked rsTooMany and will not be rescheduled?
>
> It will be marked rsTooMany or rsWillRecord depending on whether or
> not the maximum number of episodes are already recorded.  I think
> that's reasonable -- if the users wants to change the maximum episodes
> policy for that program, they should do it explicitly.  If you don't
> agree, I suggest setting recorded.preserve = 1.

Sounds quite reasonable to me as well.

Unless anyone has any objections I will go with David's suggestion of dropping
the  "AND duplicate <> 0" clause from the max episodes query in the scheduler.

I will wait a few more days before committing.

Shane