| Title | P4DTI can't handle new Bugzilla 'enum' tables |
| Status | closed |
| Priority | essential |
| Assigned user | Nick Barnes |
| Organization | Ravenbrook |
| Description | The P4DTI doesn't correctly figure out Perforce jobspec field specifications for the new implementation of Bugzilla 'enum' fields. Bugzilla used to support these fields with MySQL's 'enum' column type. Bugzilla 2.19.3 and later versions stop this (because it's not portable SQL), and instead have a separate table in the database for each such field, enumerating the possible values. The P4DTI doesn't know this, so provides a jobspec field specification of type 'text'. |
| Analysis | Bugzilla.py should spot the Bugzilla feature by the existence of these fields (e.g. bug_severity); fetch allowable values for each such field by doing a select on the table, and fake it as an enum field to the rest of the P4DTI (because we still support Bugzilla 2.18.x, which uses the old implementation, so it's best not to change the way it works in dt_bugzilla.py). |
| How found | inspection |
| Evidence | I just know |
| Observed in | 2.2.2 |
| Introduced in | 2.2.2 |
| Created by | Nick Barnes |
| Created on | 2005-10-21 13:28:27 |
| Last modified by | Nick Barnes |
| Last modified on | 2005-10-21 13:30:44 |
| History | 2005-10-21 NB Created. |