Closed
Bug 462070
Opened 17 years ago
Closed 16 years ago
Add FK constraints to the status_workflow table
Categories
(Bugzilla :: Database, enhancement)
Tracking
()
RESOLVED
FIXED
Bugzilla 3.6
People
(Reporter: LpSolit, Assigned: nbezzala)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
1.18 KB,
patch
|
mkanat
:
review+
|
Details | Diff | Splinter Review |
The old_status and new_status columns of the status_workflow table should point to bug_status.id. Not that old_status can be NULL. I hope this doesn't prevent to add the constraint to it.
|
Reporter | |
Updated•17 years ago
|
Whiteboard: [Good Intro Bug]
|
||
Comment 1•16 years ago
|
||
I can work on this. For MySQL and Oracle, the foreign keys in the referencing table can have nulls in them, so keeping old_status NULL in any row should not be a problem.
|
||
Updated•16 years ago
|
Assignee: database → vipinhegde
|
Assignee | |
Comment 2•16 years ago
|
||
Attachment #379655 -
Flags: review?(LpSolit)
|
|
Reporter | |
Updated•16 years ago
|
Attachment #379655 -
Flags: review?(LpSolit) → review?(mkanat)
|
|
||
Updated•16 years ago
|
Attachment #379655 -
Flags: review?(mkanat) → review+
|
|
||
Updated•16 years ago
|
Assignee: vipinhegde → nbezzala
Flags: approval+
Whiteboard: [Good Intro Bug]
Target Milestone: --- → Bugzilla 3.6
|
|
Reporter | |
Comment 3•16 years ago
|
||
Checking in Bugzilla/DB/Schema.pm;
/cvsroot/mozilla/webtools/bugzilla/Bugzilla/DB/Schema.pm,v <-- Schema.pm
new revision: 1.119; previous revision: 1.118
done
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•