[mythtv-commits] Ticket #3976: svn trunk: mythweb: creating a custom schedule with title search generates an invalid query

[MythTV]

#3976: svn trunk: mythweb: creating a custom schedule with title search generates
an invalid query
-----------------------+----------------------------------------------------
 Reporter:  anonymous  |        Owner:  kormoc    
     Type:  defect     |       Status:  closed    
 Priority:  minor      |    Milestone:  0.21      
Component:  mythtv     |      Version:  unknown   
 Severity:  medium     |   Resolution:  worksforme
  Mlocked:  0          |  
-----------------------+----------------------------------------------------

Comment(by simonwalls at yahoo.com):

 I have reproduced this on 0.21-fixes svn 18900. The way it is provoked is
 to create a new custom search, specify a Title for the search, but not
 fill in the 'Search String' field.

 This is easily done if you are in a hurry (and maybe it's the first time
 you've used that page). The 'Title' of the search and the 'string to
 search for' are often the same. The two form boxes are adjacent to each
 other and maybe you think that the second one is optional. Unfortunately
 there's not a check for a null string on the Search String when a Title
 Search is submitted.

 I've included the contents of my mythconverg database for two examples,
 both were created in mythweb, but of these only item number 356 generates
 an "Invalid search key in recordid" message in mythbackend.log.

 {{{
 recordid        type      chanid  starttime        startdate       endtime
 enddate         title     subtitle        description     category
 profile recpriority     autoexpire      maxepisodes     maxnewest
 startoffset     endoffset       recgroup        dupmethod       dupin
 station seriesid        programid       search  autotranscode
 autocommflag    autouserjob1    autouserjob2    autouserjob3
 autouserjob4    findday findtime        findid  inactive        parentid
 transcoder      tsdefault       playgroup       prefinput
 next_record     last_record     last_delete     storagegroup    avg_delay
 356                4       1001    22:19:22        2008-11-24
 22:19:23        2008-11-24      Sky High (Title Search)
 Custom recording        Default 0       0       0       0       0       0
 Default 6       15      BBC ONE                 2       0       1       0
 0       0       0       1       22:11:22        733736  0       0       0
 1       Default 0       0000-00-00 00:00:00     2008-11-26 19:49:15
 0000-00-00 00:00:00     Default 100
 368                4       1001    17:46:08        2008-11-27
 17:46:09        2008-11-27      SkyHigh (Title Search)          sky high
 Custom recording        Default 0       0       0       0       0       0
 Default 6       15      BBC ONE                 2       0       1       0
 0       0       0       1       17:11:08        733739  0       0       0
 1       Default 0       0000-00-00 00:00:00     0000-00-00 00:00:00
 0000-00-00 00:00:00     Default 100
 }}}

 You can see that the 'description' field is null on 356. This comes from
 the search string field on the mythweb page.

 I don't have the ability right now to write a patch for mythweb that would
 check for a null Search String (in a Title Search only), but having that
 would avoid entries like 356 above getting in the database and causing the
 'Invalid search key' message.

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/3976#comment:4>
MythTV <http://www.mythtv.org/>
MythTV