[mythtv-commits] Ticket #9875: Multiple setting definitions in mythconverg.settings

[MythTV]

#9875: Multiple setting definitions in mythconverg.settings
------------------------------------+-----------------------------
 Reporter:  fraser@…                |          Owner:
     Type:  Bug Report - General    |         Status:  closed
 Priority:  minor                   |      Milestone:  unknown
Component:  MythTV - General        |        Version:  Unspecified
 Severity:  low                     |     Resolution:  Won't Fix
 Keywords:  database, settings      |  Ticket locked:  0
------------------------------------+-----------------------------
Changes (by robertm):

 * status:  new => closed
 * resolution:   => Won't Fix


Comment:

 While it's a fact that you *can* have duplicate values in the settings
 table, the reality is that under normal use cases, this won't generally
 actually occur.  This problem is generally limited to extreme scenarios or
 instances where the user takes it upon themselves to manipulate the
 database manually.

 This is not to say that we couldn't be doing more to prevent insertion of
 duplicate values, but there are a number of reasons we have to leave it
 the way it is, and unless a bug submitter can point to a particular
 scenario that the average user will encounter that can create duplicate
 values, this bug will sit open and untouched for literally years.  As we
 already have hundreds of bugs that have sat open for years, I'm opting to
 close this one now rather than wait until 2014 to do it.

 If you can find a repeatable test case where you can get the *UI* to
 insert multiple duplicate values in the DB, then we can handle those on an
 individual basis.  This ticket is just too broad and too unlikely to ever
 be changed to allow to sit open.

 All the user job settings are in mythtv-setup, including the one you
 manipulated manually (case in point).

-- 
Ticket URL: <http://code.mythtv.org/trac/ticket/9875#comment:2>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center