Ravenbrook / Projects / Perforce Defect Tracking Integration / Version 1.0 Product Sources / Design

Perforce Defect Tracking Integration Project

Bugzilla database schema extensions for integration with Perforce

Nicholas Barnes, Ravenbrook Limited, 2000-11-14

1. Introduction

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.

2. Notes on the schema extensions

placeholder

3. The schema extensions

The "p4dti_bugs" table

Field Type Default Properties Remarks
bug_id mediumint(9) 0    
rid varchar(32)      
sid varchar(32)      
jobname text None    
replication datetime 0000-00-00 00:00:00    
action text None    

Indices:

Name Fields Unique?
primary bug_id yes

The "p4dti_bugs_activity" table

Field Type Default Properties Remarks
bug_id mediumint(9) 0    
who mediumint(9) 0    
bug_when datetime 0000-00-00 00:00:00    
fieldid mediumint(9) 0    
oldvalue tinytext None null  
newvalue tinytext None null  
rid varchar(32)      
sid varchar(32)      

Indices:

Name Fields Unique?
bug_id bug_id  
bug_when bug_when  

The "p4dti_changelists" table

Field Type Default Properties Remarks
changelist int(11) 0    
rid varchar(32)      
sid varchar(32)      
user mediumint(9) 0    
flags int(11) 0    
description longtext None    
client text None    
p4date text None    
replication datetime 0000-00-00 00:00:00    

Indices:

Name Fields Unique?
changelist changelist, rid, sid yes

The "p4dti_config" table

Field Type Default Properties Remarks
rid varchar(32)      
sid varchar(32)      
config_key text None    
config_value longtext None null  

Indices:

Name Fields Unique?
rid rid, sid  

The "p4dti_filespecs" table

Field Type Default Properties Remarks
bug_id mediumint(9) 0    
rid varchar(32)      
sid varchar(32)      
replication datetime 0000-00-00 00:00:00    
filespec longtext None    

Indices:

Name Fields Unique?
bug_id bug_id  

The "p4dti_fixes" table

Field Type Default Properties Remarks
changelist int(11) 0    
bug_id mediumint(9) 0    
rid varchar(32)      
sid varchar(32)      
user mediumint(9) 0    
client text None    
status text None    
p4date text None    
replication datetime 0000-00-00 00:00:00    

Indices:

Name Fields Unique?
changelist changelist, bug_id, rid, sid yes
bug_id bug_id  

The "p4dti_replications" table

Field Type Default Properties Remarks
rid varchar(32)      
sid varchar(32)      
start datetime 0000-00-00 00:00:00    
end datetime 0000-00-00 00:00:00    

Indices:

Name Fields Unique?
rid rid, sid, start yes
end end  
h2>4. Example queries

placeholder

A. References

[RB 2000-08-30] "Design document structure" (e-mail message); Richard Brooksby; Ravenbrook Limited; 2000-08-30.
[RB 2000-10-05] "P4DTI Project Design Document Procedure"; Richard Brooksby; Ravenbrook Limited; 2000-10-05.

B. Document History

2000-11-14 NB Created.
2001-03-02 RB Transferred copyright to Perforce under their license.

This document is copyright © 2001 Perforce Software, Inc. All rights reserved.

Redistribution and use of this document in any form, with or without modification, is permitted provided that redistributions of this document retain the above copyright notice, this condition and the following disclaimer.

This document is provided by the copyright holders and contributors "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the copyright holders and contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this document, even if advised of the possibility of such damage.

$Id: //info.ravenbrook.com/project/p4dti/branch/2001-03-12/integration-kit/design/bugzilla-p4dti-schema/index.html#2 $

Ravenbrook / Projects / Perforce Defect Tracking Integration / Version 1.0 Product Sources / Design