[mythtv-users] are rules case sensitive?

[blind Pete]

On Wed, 26 Nov 2014 09:32:50 -0500
"Michael T. Dean" <mtdean at thirdcontact.com> wrote:

> On 11/26/2014 04:45 AM, Stephen Worthington wrote:
> > On Wed, 26 Nov 2014 19:19:59 +1100, you wrote:
> >
> >> Hi *,
> >>
> >> Should a custom rule, "program.title LIKE '%vikings%'" find a
> >> program called "Vikings"?  There is such a rule on my machine, and
> >> tomorrow night's program is being ignored.  The guide shows the
> >> program, but "mythbackend --printsched" does not.  The previous
> >> season worked. Is there a list of stupid things that I might have
> >> done to upset it?
> > The rule is just SQL - so it follows the MySQL rules.  So yes, it
> > should be doing a case insensitive match.
> 
> unless you've corrupted your schema.
> 
> That said, the easiest way to find out if it's case sensitive is to
> try using a capital V and see if anything changes...
> 
> > It is possible that the scheduler thinks that this match has been
> > previously recorded, and so will not record it again.  I would
> > suggest going to the program in the guide and seeing what it is
> > flagged as. Or go to Manage Recordings>  Recording Rules and use
> > Ctrl-S to search for your rule, then use the O key to see all the
> > listings that currently match that rule.  You may see that all of
> > the matching listings are greyed out as not going to be recorded
> > for one reason or another.  If there are no matches for the rule,
> > then I have no clue as to why it would not match.
> 
> Or it's possible that MythTV thinks that showing cannot be
> recorded--i.e. due to Input Connections configuration issues.
> 
> Mike

The "this day and time" filter triggers the bad behaviour.  (As
does the "this day" filter.)  

There are now four listings in the guide;
HD and SD tonight and same again next week.  Surely "day and time"
should catch one per week?

Next question; why is it preferring HD?  I thought that it was set to
prefer SD.  

-- 
testing
bP