Title | P4DTI can't handle null fields in Bugzilla |
Status | closed |
Priority | essential |
Assigned user | Nick Barnes |
Organization | Ravenbrook |
Description | Bugzilla now (2.20) has some 'null' columns in the bugs table (i.e. fields which are allowed to have a null value). For instance, the qa_contact field can be null. These fields are not properly set in Bugzilla when replicating or creating a new bug (the qa_contact field is set from the initial_qacontact field in the components table, which may also be null). |
Analysis | sql_quote in bugzilla.py needs to convert None into 'null'. |
How found | automated_test |
Evidence | Migration and new_p4_job tests. |
Observed in | 2.2.2 |
Test procedure | test_p4dti.new_p4_job. |
Created by | Nick Barnes |
Created on | 2005-10-21 13:37:23 |
Last modified by | Nick Barnes |
Last modified on | 2005-10-21 13:38:02 |
History | 2005-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. |