[mythtv-users] scheduler confusion

[blind Pete]

On Mon, 01 Sep 2014 12:48:55 -0500
Bill Meek <keemllib at gmail.com> wrote:

> On 09/01/2014 04:37 AM, blind Pete wrote:
> > On Sun, 31 Aug 2014 20:07:25 -0500
> > Bill Meek <keemllib at gmail.com> wrote:
> ...
> > I am not brave enough to edit the database directly, although I will
> > poke around and look with the command line.
> 
> Understood, I wasn't suggesting direct DB changes, what you said below
> is spot on.
> 
> > The changes were made through the frontend's main menu
> >   -> Utilities/Setup
> >   -> Setup
> >   -> TV Settings
> >   -> Recording Priorities
> >   -> Custom Priority Rules
> 
> > If nothing complained I assumed that there were no gross errors,
> > like comparing an int to a string, but that was just an assumption.
> 
> I added a Custom Priority Rule with a text cardid and got no
> errors, and there were no errors in the BE log even with
> -v schedule, database when it used the rule.
> 
> >> selectclause: (channel.callsign LIKE 'SBS%' OR channel.callsign =
> >> 'NITV') AND cardinput.cardid = 'sbs' selectclause:
> >> cardinput.cardid = 'abc' AND channel.callsign LIKE 'abc%'
> >> selectclause: (channel.callsign NOT LIKE ('SBS%') AND
> >> channel.callsign <> 'NITV' ) AND cardinput.cardinputid <> 'sbs'
> >> selectclause: channel.callsign NOT LIKE 'abc%' AND
> >> cardinput.cardid = 'sbs'
> >>
> >
> > You might be right, this might be complete and utter gibberish, but
> > it is not the cause of the trouble.
> 
> OK, saw it in the 1st post and misunderstood its importance.
> 
> > Now that you are here; if cardinput.cardinputid is an int and lower
> > case 'sbs' is a string rather than a label with an int value, where
> > would the error messages be?  Can you recommend an SQL primer?  Or a
> > cheat sheet that lists arithmetic, string, and logical operators.
> 
>      http://www.mythtv.org/wiki/Cardinput_table.

This link was useful information.  

> You can lookup any table on the Wiki or just use: SHOW COLUMNS FROM
> someTableName; I prefer that just in case the Wiki isn't up to date.
> 
> I tried: SELECT cardid FROM cardinput WHERE cardid = 'abc'; and a
> warning is printed if you first turn warnings on by typing: \W

Just using the GUI; Custom Priority Rules and clicking on "test"  
will through up errors for things like "AND AND".  

-- 
testing
bP