| Title | Can't handle new Bugzilla product and component tables |
| Status | closed |
| Priority | essential |
| Assigned user | Nick Barnes |
| Organization | Ravenbrook |
| Description | Replicating product or component fields from Bugzilla 2.18 will not work because of a Bugzilla database schema change. |
| Analysis | The bugs table doesn't have columns called "product" and "component" any more; they have been replaced by numeric IDs keying into the "products" and "components" tables. This is invisible to the user, who just sees the product or component name. Change bugzilla.py so that it can identify a Bugzilla schema which has numeric product/component IDs. If working with such a schema, bugzilla.py should look up product and component values for each bug and add them to the dictionary for a bug as if they were present directly in the bugs table. It also must add entries to the table of column types produced by get_types, so that configure_bugzilla can generate an appropriate jobspec. |
| How found | inspection |
| Evidence | <http://www.ravenbrook.com/project/p4dt...ster/design/bugzilla-schema/#table-bugs> |
| Observed in | 2.1.2 |
| Introduced in | 2.0.0 |
| Created by | Nick Barnes |
| Created on | 2004-06-24 12:12:48 |
| Last modified by | Nick Barnes |
| Last modified on | 2004-07-16 13:55:21 |
| History | 2004-06-24 NB Created. |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 97171 | closed | 2004-05-28 16:43:43 | Nick Barnes | Bugzilla 2.17.7 support: bugmail.pl replacement for processmail. Bugzilla 2.17.5 database schema changes (especially new groups system, new product and component IDs, group_control_map controls); Cache results of some database queries to speed operation with new or old schemas; Changed bug change permission rules; Clean up better when deleting a bug; Correct values in bugs_activity entries when changing user columns. |