P4DTI issue job001259

TitleP4DTI can't handle new Bugzilla 'enum' tables
Assigned userNick Barnes
DescriptionThe 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'.
AnalysisBugzilla.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 foundinspection
EvidenceI just know
Observed in2.2.2
Introduced in2.2.2
Created byNick Barnes
Created on2005-10-21 13:28:27
Last modified byNick Barnes
Last modified on2005-10-21 13:30:44
History2005-10-21 NB Created.


Change Effect Date User Description
155470 closed 2005-10-19 18:19:33 Nick Barnes Numerous changes to bring P4DTI up-to-date with Bugzilla 2.20 and unicode Perforce servers.
155236 open 2005-10-04 16:00:21 Nick Barnes Handle Bugzilla 2.20 enumeration tables.