Bug 408761

Summary: Update Bugzilla/DB/Schema.pm to add in changes from rh_bugzilla_2_18 schema
Product: [Community] Bugzilla Reporter: David Lawrence <dkl>
Component: DatabaseAssignee: Tony Fu <tfu>
Status: CLOSED DUPLICATE QA Contact:
Severity: low Docs Contact:
Priority: high    
Version: 3.2   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: https://engineering.redhat.com/rt3/Ticket/Display.html?id=18295
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-12-12 05:00:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 406071    
Attachments:
Description Flags
HTML file comparing 3.0 schema with RH 2.18 schema none

Description David Lawrence 2007-12-03 15:44:19 UTC 
Description of problem:
We need to add tables/columns current in rh_bugzilla_2_18 that are being
actively used by Red Hat. This will allow a clean migration of our current
snapshots to a fresh 3.0 database created by checksetup.pl.

We can use Noura's output from her db schema script to determine that needs to be 
moved over.

The critical things we need to look at when migrating our data are:

1. The tables/columns that are in purple will need to be added to the
Bugzilla/DB/Schema.pm file.
2. The columns that are in yellow that have a NOT NULL constraint will need to
be set to NULL when we import the data. Then we will need to go back and set 
the values to something appropriate and re-instate the NOT NULL restriction. The
alternative would be to somehow insert appropriate values for the new columns
when the data is imported. That may prove to be more difficult to implement.
3. The new tables marked with yellow may need some default list to be populated
so cannot be left empty when the data base is created. So we may need to alter
checksetup.pl to auto-populate the new tables but leave the old ones empty for
our imported data.

Attaching the output file containing the comparison.
Comment 1 David Lawrence 2007-12-03 15:44:19 UTC 
Created attachment 275761 [details]
HTML file comparing 3.0 schema with RH 2.18 schema
Comment 2 David Lawrence 2007-12-12 05:00:56 UTC 

*** This bug has been marked as a duplicate of 420611 ***