Options table contains duplicate OptionKey rows
Bug #324364 reported by
TJ
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Tracker |
Fix Released
|
Medium
|
|||
| tracker (Ubuntu) |
Triaged
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: tracker
Affects: Hardy Intrepid Jaunty
Whilst working on other bugs I discovered that the Options table can accept multiple entries for the same OptionKey.
I've reported it upstream and, if they resolve it, will create a patch based on their fix.
| Changed in tracker: | |
| status: | Unknown → New |
| Changed in tracker: | |
| assignee: | nobody → intuitivenipple |
| status: | New → Confirmed |
| Changed in tracker (Ubuntu): | |
| assignee: | intuitivenipple → nobody |
| status: | Confirmed → Triaged |
| Changed in tracker: | |
| status: | New → Fix Released |
| Changed in tracker: | |
| importance: | Unknown → Medium |
To post a comment you must log in.
Upstream's trunk is a totally re-written code-base. However they have confirmed the required changes and I am working up a patch which also needs to fix-up existing user common.db Options table format. This is closely linked to bug #324300 "Incorrect parameter order for SetOption".
In this case the problem is that the table was not created with a PRIMARY KEY.