[mythtv-users] Slow MySQL query after delete

[Jay R. Ashworth]

On Fri, Sep 07, 2007 at 12:45:55AM -0400, Michael T. Dean wrote:
> Keeping your recording schedule clean of unwanted items is A Good
> Thing.  And, duplicates of actually in-use rules (as opposed to rules
> for canceled shows) doubles the positives for that rule (plus the
> previously-recorded), making query processing significantly harder.  So
> in your case, you had a double whammy of unnecessary rules and
> duplicates (or would that be a 12-tuple, or a double and a decuple, or
> maybe a dodecuple(?) whammy with your 12 copies of the one rule?).

Isn't there a way to UNIQ out duplicates in those tables?  Or is the
BUSQ too tense already?

> I'm also a big fan of the don't optimize before profiling approach, so
> that's why I /always/ recommend users use "any channel" rules.  /If/
> they see a problem, they can then choose to "optimize," but premature
> optimization typically causes more problems than designing (recording
> rules, in this case) for maintenance.  (So now those of you who have, in
> the last few days, mentioned my recommending "any channel" rules know
> why I do so.)

Ah... A Jon Bentley fan.  :-)

Cheers,
-- jra
-- 
Jay R. Ashworth                   Baylink                      jra at baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com                     '87 e24
St Petersburg FL USA      http://photo.imageinc.us             +1 727 647 1274