[mythtv-commits] Ticket #7467: Watch recordings screen will not load if bookmark column contains "invalid" value

[MythTV]

#7467: Watch recordings screen will not load if bookmark column contains "invalid"
value
-------------------------------------------+--------------------------------
 Reporter:  skd5aner <skd5aner@…>          |        Owner:  ijr    
     Type:  defect                         |       Status:  closed 
 Priority:  minor                          |    Milestone:  unknown
Component:  MythTV - General               |      Version:  0.22rc1
 Severity:  medium                         |   Resolution:  wontfix
  Mlocked:  0                              |  
-------------------------------------------+--------------------------------
Changes (by mdean):

  * status:  new => closed
  * resolution:  => wontfix


Comment:

 This issue is due to a bug in Qt4 that causes QSqlQuery::next() to fail on
 a record containing a TINYINT(1) field where the column value is less than
 -9 or greater than 99.

 After discussion in IRC, we have decided not to work around the Qt bug in
 MythTV at this time.  If a lot more users than we expect experience this
 issue, we will consider adding a workaround.

 The only users who could possibly be affected by this issue (ignoring the
 possibility of users manually editing DB data) are users who upgraded to
 trunk MythTV between [9270] (Mar 6, 2006 05:30:05 AM) and [11016] (Sep 2,
 2006 08:59:13 AM) and who still have recordings more than 3 years and 2
 months old.  Further, most of those users no longer have the invalid data
 in their databases.  The invalid data will only exist for users who:

  * Upgraded to trunk between [9270] and [11016] (both changes during the
 0.19 to 0.20 development cycle
  * Had one or more recordings with bookmarks set at the time
  * Still have one or more of those recordings that had bookmarks
  * Have never changed the bookmark on the recording(s)

 Any users who experience the issue may fix their data by running:
 {{{
 mysql -umythtv -p mythconverg -e "UPDATE recorded SET bookmark = 1 WHERE
 bookmark != 0;"
 }}}
 Please feel free to mention to me in IRC (sphery) or send a message to the
 list if you are affected by this issue.

 Thanks to Matt S., Brad Templeton, and Kevin Khupal for the identifying
 the invalid data that tripped the Qt bug, and to Matt S. for reporting the
 issue so we could fully understand what's happening.

 (Note for me:  Likely workaround would be to modify all queries in
 0.22-fixes that access the bookmark field to use "bookmark + 0" rather
 than "bookmark" to retrieve the field contents and add an appropriate
 comment explaining the hack; then add a DB update to trunk to "UPDATE
 recorded SET bookmark = 1 WHERE bookmark != 0;" so that the
 workaround/hack is not necessary in trunk going forward.)

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