| Title | Can't upgrade Bugzilla integration cleanly |
| Status | closed |
| Priority | essential |
| Assigned user | Nick Barnes |
| Organization | Ravenbrook |
| Description | If the P4DTI changes in such a way that the Bugzilla P4DTI database schema is changed, then existing users upgrading to the new P4DTI will have problems because of the changed schema. |
| Analysis | Add a schema_version to the p4dti_config table. Code can then notice schema changes and handle them (e.g. by dropping the existing tables and creating new ones). |
| How found | inspection |
| Evidence | I just know. |
| Observed in | 1.0.6 |
| Introduced in | 1.0.0 |
| Created by | Nick Barnes |
| Created on | 2001-04-09 15:43:00 |
| Last modified by | Gareth Rees |
| Last modified on | 2001-12-10 19:38:10 |
| History | 2001-04-09 NB Created. 2001-04-09 RB Set priority to essential. |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 10806 | closed | 2001-03-29 14:04:06 | Nick Barnes | Bugzilla schema changes working. |
| 10805 | open | 2001-03-29 13:59:18 | Nick Barnes | Added schema version management, so schema changes can be handled when upgrading. |