Bugzilla::User::Setting should use Bugzilla::Object

NEW
Unassigned

Status

()

--
enhancement
11 years ago
7 years ago

People

(Reporter: mkanat, Unassigned)

Tracking

(Blocks: 1 bug)

Details

(Reporter)

Description

11 years ago
Right now Bugzilla::User::Setting does ridiculous funky custom stuff that's actually very inefficient, and it should instead be using Bugzilla::Object, at *least* for new(), and we should replace get_all_settings with new_from_list.

I suppose the tricky bit is that settings don't have numeric IDs, but we can deal with that by making the ID_FIELD equal to the NAME_FIELD.

Updated

9 years ago
Blocks: 355838

Comment 1

7 years ago
We are going to branch for Bugzilla 4.4 next week and this bug is either too invasive to be accepted for 4.4 at this point or shows no recent activity. The target milestone is reset and will be set again *only* when a patch is attached and approved.

I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else.
Target Milestone: Bugzilla 4.4 → ---
You need to log in before you can comment on or make changes to this bug.