Ravenbrook / Projects / Perforce Defect Tracking Integration / Master Product Sources / Design
Perforce Defect Tracking Integration Project
This document defines Bugzilla database schema extensions for integrating with Perforce.
The purpose of this document is to make sure that Bugzilla and the P4DTI replicator are consistent in their treatment of these relations.
This document will be modified as the product is developed.
The intended readership is P4DTI developers.
This document is not confidential.
placeholder
placeholder
placeholder
[RB 2000-08-08] | "P4DTI Design Meetings with Perforce" Richard Brooksby; Ravenbrook Limited; 2000-08-08. |
[RB 2000-08-10] | "Replication mapping design notes" (e-mail message); Richard Brooksby; Ravenbrook Limited; 2000-08-10 11:27:03 GMT. |
[RB 2000-10-05] | "P4DTI Project Design Document Procedure"; Richard Brooksby; Ravenbrook Limited; 2000-10-05. |
[RB 2000-08-30] | "Design document structure" (e-mail message); Richard Brooksby; Ravenbrook Limited; 2000-08-30. |
[Fish 2000-09-06] | "RE: TeamTrack database schema extensions for integration with Perforce" (e-mail message); Larry Fish; TeamShare Limited; 2000-09-06 00:30:28 GMT. |
[GDR 2000-08-18] | "TeamShare design meetings, 2000-08-14/2000-08-16"; Gareth Rees; Ravenbrook Limited; 2000-08-18. |
[GDR 2000-09-06a] | "RE: TeamTrack database schema extensions for integration with Perforce" (e-mail message); Gareth Rees; Ravenbrook Limited; 2000-09-06 10:11:04 GMT. |
[GDR 2000-09-06b] | "TeamTrack sample data"; Gareth Rees; Ravenbrook Limited; 2000-09-06. |
[GDR 2000-10-10] | "Defect in schema definition now fixed" (e-mail message); Gareth Rees; Ravenbrook Limited; 2000-10-10 16:41:25 GMT. |
[GDR 2000-10-11] | "Re: Design Discussion: modified time in the VCACTIONS table" (e-mail message); Gareth Rees; Ravenbrook Limited; 2000-10-11 09:29:41 GMT. |
[van Rossum 2000-03-22] | "Python Reference Manual (Release 1.5.2)"; Guido van Rossum; Corporation for National Research Initiatives; 2000-03-22. |
2000-09-04 | GDR | Created based on [RB 2000-08-10], [RB 2000-08-18], [RB 2000-08-30] and [GDR 2000-08-18]. Fixed defects discovered in review with RB. |
2000-09-06 | GDR | Added clarifications from my e-mail to Larry Fish [GDR 2000-09-06a] in response to his questions [Fish 2000-09-06]. Added reference to sample data [GDR 2000-09-06b]. Added note about modification times. |
2000-09-10 | GDR | Added description of TS_P4DTI_REPLICATED field in the
TS_CASES table. |
2000-09-11 | GDR | Added example queries (section 4). |
2000-09-13 | GDR | Explained how fields get added to the TS_CASES table
(section 2.6). Listed the fields which it
would be sensible to index (section
2.7). |
2000-10-05 | RB | Updated reference to design document procedure [RB 2000-10-05] to point to on-line document. |
2000-10-10 | GDR | Removed SID and SERVER_DESCRIPTION keys
from the replicator configuration in the VCACTIONS table
(because they don't support the possibility of a replicator
replicating to more than one server). Added SERVER key
which does. See [GDR 2000-10-10]. |
2000-10-11 | GDR | Made description of TS_TIME2 field in the
VCACTIONS table clearer: it's now clear who requires it
to be 0 and when. See [GDR
2000-10-11]. |
Copyright © 2000 Ravenbrook Limited. This document is provided "as is", without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this document. You may make and distribute copies and derivative works of this document provided that (1) you do not charge a fee for this document or for its distribution, and (2) you retain as they appear all copyright and licence notices and document history entries, and (3) you append descriptions of your modifications to the document history.
$Id: //info.ravenbrook.com/project/p4dti/branch/2000-11-29/bugzilla-resolution/design/bugzilla-p4dti-schema/index.html#1 $
Ravenbrook / Projects / Perforce Defect Tracking Integration / Master Product Sources / Design