[mythtv] Re: Re: [PATCH] delete recording schedules

[Bruce Markey]

Jeremiah Morris wrote:
> On 2 Apr 2005, at 1:03 PM, David Engel wrote:
> 
>> If a recording ends at 3am and mythfilldatabase runs a 4am, that is
>> not when "mythfilldatabase runs the next day".
> 
> 
> My mistake -- it's a random time between 4 and 28 hours, then, not a 
> random time between 0 and 24 hours. I fail to see that as a significant 
> improvement.
> 
>> It makes perfect sense because mythfilldatabase is where any database
>> housekeeping is done.
> 
> 
> If it's an integral part of the housekeeping process, why is it included 
> in a separate binary and run as frequently or infrequently as the user 
> specifies? That is necessary for filling the database, where the 
> procedure may involve custom jobs in the data grabbing, but not for 
> normal mythbackend housekeeping.

First of all, you're getting way too worked up about a small thing
and this reeks of creating argument for the sake of 'I'm right'
rather than exchanging information.

Getting new listings is the most important housekeeping there is.
If you don't get new listings, none of this matters anyway =). Like
it or not, mfdb does clear out the trash and fixes up tables other
than just 'program'.

>> "completes successfully" is a misnomer.  That code runs when a
>> recording is stopped for any reason and includes the cases where the
>> user manually stops or deletes a recording while it is still in
>> progress.
> 
> 
> Okay, I had assumed "prematurestop" in the code meant "prematurely 
> stopped", not "stopped due to error". Does Myth know when a recording is 
> truly actually finished, then?

No. Do we as humans know ;-)? You could add to the end time and restart.

>>   Stopping or deleting prematurely are specific cases the
>> reactivation logic is meant to handle.
> 
> 
> Can someone provide a use case for reactivation? 

1) He just did. 2) Are you arguing that such a feature should not
exist?

> I just can't imagine 
> choosing to delete a recording, and then wanting to start it again, and 
> not caring that I missed some in the middle.

Nothing in his comment indicates not caring. Perhaps a glass of
Lemonade before you reply again may help.

If more than one thing is recording and and you hit Stop on the
wrong one for starters but here are some things that I've actually
done that I can remember.

- Though it hasn't happened to me lately, if a recording starts up
with a problem like bad parameters or is hozed in some other way,
Stop and Reactivate.

- If something like a sports event started with a different Profile
than I intended I may change the option then Stop and Reactivate.

- If the master crashes during a recording of an episode that has a
later showing, on restart the scheduler (correctly) prefers the
complete later showing and marks the current one L. I may choose
to Reactive the current showing and may or may not choose to record
the later showing. This happened to me just last night during the
first showing of the finale of Invasion Iowa.

- If a game gets assigned to a different card/host than I would
have preferred, I may change priorities then Stop and Reactivate.

- If I see a showing that is marked P,L,E or whatever and I'd like
to see part of it now for whatever reason I may Reactivate.

- During a six hour Golf broadcast (which I'll watch in under an
hour and a half) I may Stop and Reactivate in the middle then
watch and delete the first part rather than having it all in one
big file. I'm not saying this is necessary but it's something I've
done.

And so on. This is a very useful feature.

--  bjm