[mythtv-commits] Ticket #3426: mythrename.pl can't rename

MythTV mythtv at cvs.mythtv.org
Mon May 7 21:08:35 UTC 2007


#3426: mythrename.pl can't rename
-----------------------+----------------------------------------------------
 Reporter:  anonymous  |        Owner:  ijr    
     Type:  defect     |       Status:  new    
 Priority:  minor      |    Milestone:  unknown
Component:  contrib    |      Version:  unknown
 Severity:  low        |   Resolution:         
-----------------------+----------------------------------------------------

Comment(by sphery <mtdean at thirdcontact.com>):

 The use of starttime is correct.  The use of progstart is incorrect.
 There is only one progstart for each program (i.e. the scheduled program
 start time), but there could be 2 or 3 or 4 or ... starttime's for
 recordings of that same program if recording is interrupted (i.e. exiting
 LiveTV without hitting record then re-entering, changing channels in
 LiveTV, or due to backend shutdowns/crashes during recording).  So the
 patch you've uploaded will actually corrupt databases in certain
 situations (I hope yours not included).

 However, in the Perl bindings, what the DB calls starttime is called
 starttime (and the MythTV C++ code calls it startts).  What the DB calls
 progstart, the Perl bindings and the MythTV C++ code calls recstartts.
 mythrename.pl should be using recstartts for finding recordings, not using
 starttime.  So, mythtv-mythrename-use_recording_start_time.patch should
 fix the bug you found.

 So, the question now is, was my use of "one-year-apart" (rather than "one-
 day-apart") a typo/read-o or an inside joke/challenge to try to convince
 you of the importance of verifying the data you're using to point out bugs
 because of the impossibility of properly diagnosing a bug with bad data.
 :)

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


More information about the mythtv-commits mailing list