Opened 12 years ago

Closed 12 years ago

#3936 closed patch (fixed)

Fix for mixed category name case sensitivity in program list (+simple workaround)

Reported by: anonymous Owned by: Isaac Richards
Priority: minor Milestone: 0.21
Component: mythtv Version: head
Severity: low Keywords: category
Cc: Ticket locked: no

Description

Up until recently the radio times list all films (movies ;-) ) with the category 'film', then they changed to 'Film' (with a period in between where they couldn't seem to decide and used both).

I have my program list screen configured to 'Categories only'. When a program of the 'Film' category was recorded the 'film' category was no longer listed due to a case sensitivity mismatch in playbackbox.cpp.

The obvious work around is to change all the programs to have the same category (in mysql) :

update recorded set category="film" where category="Film" ;

However, for the period where to listing provider vacillated between the two the list of 'films' would be unreliable.

Attached patch removes the case insensitivity from sortedList, this means that if there are categories 'Film' and 'film' both will get listed, although this isn't very pretty I think its better to have a user ask 'Lawks, why do I have two film categories?' rather than 'Crivens! Where's all my films gone?!'.

Attachments (1)

category_patch.diff (651 bytes) - added by bbennetts@… 12 years ago.
Patch for category case sensitivity mix.

Download all attachments as: .zip

Change History (4)

Changed 12 years ago by bbennetts@…

Attachment: category_patch.diff added

Patch for category case sensitivity mix.

comment:1 Changed 12 years ago by paulh

Resolution: invalid
Status: newclosed

It looks like this problem shouldn't occur anymore at least if you are using trunk. The categories are fixed in mythfilldatabase now. http://svn.mythtv.org/trac/changeset/13774

comment:2 Changed 12 years ago by stuartm

Milestone: 0.21
Resolution: invalid
Status: closedreopened
Version: 0.20-fixeshead

13374 didn't address problems with EIT. But the problem was fixed properly with [14670], I just didn't notice this ticket at the time.

comment:3 Changed 12 years ago by stuartm

Resolution: fixed
Status: reopenedclosed
Note: See TracTickets for help on using tickets.