[mythtv] (How) does allow re-record work?
David Engel
david at istwok.net
Wed Jul 25 20:15:16 UTC 2007
On Wed, Jul 25, 2007 at 09:59:48AM -0700, Bruce Markey wrote:
> David Engel wrote:
> > the duplicate setting in recorded and oldrecorded. oldfind is an
> > imperfect optimization to avoid greatly increasing the time needed for
> > the big scheduler query.
>
> That's true too but the real reason for oldfind is that a search
> rule may not be able to match by title. For instance, a FindWeekly
> "Bill Murray (People Search)" needs to know that "Meatballs" is a
> dup for this week if "Stripes" has already been recorded. Oldfind
> tracks if the rule (recordid) has recorded in the current time
> interval (findid). When a recording has a findid, ForgetHistory()
> and DeleteHistory() update oldfind while updating oldrecorded.
That's because the oldrecduplicate join on old recorded is broken with
respect to find rules. Likewise for the recduplicate join on
recorded. I've tried fixing it at least a couple of times but the fix
always turns out to be more painful time-wise than the bug. In
addition, the findduplicate join on oldfind has a bug with respect to
overrides.
As luck would have it, only the most obscure, some would say
contrived, cases get through the two bugs, so I've left them alone.
Hence, my characterization of oldfind quoted above.
David
--
David Engel
david at istwok.net
More information about the mythtv-dev
mailing list