Closed
Bug 543102
Opened 15 years ago
Closed 15 years ago
column isactive in table for customfields - not used?
Categories
(Bugzilla :: Creating/Changing Bugs, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 456743
People
(Reporter: werner.moser, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729) Build Identifier: bugzilla 3.4.4 I have created some custom fields of type drop down and after a while set isactive=0 for outdated values. These values still appear in the dropdown list and generate an error when one of them is selected. Is the column isactive not used (it cannot be set using bugzilla, only using sql...)? What is its purpose? Reproducible: Always Expected Results: It would be very helpful, if values with isactive=0 are excluded. quick hack of mine in Object.pm, function sub _do_list_select: my $sql = "SELECT $cols FROM $table"; #hack to exclude inactive values if (substr($table,0,3) eq 'cf_'){ if (defined $where) { $where .= " and isactive=1 "; } else { $where = " isactive=1 "; } } #hack-end if (defined $where) {
Reporter | ||
Comment 1•15 years ago
|
||
Any feedback would really be appreciated.
Comment 2•15 years ago
|
||
You are not supposed to play with the DB directly. That's most of the time a bad idea. Anyway, isactive is now in use in Bugzilla 3.6 for custom fields.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Version: unspecified → 3.4.4
You need to log in
before you can comment on or make changes to this bug.
Description
•