Closed
Bug 460922
Opened 17 years ago
Closed 17 years ago
[Oracle] Need to drop all the FKs before dropping tables.
Categories
(Bugzilla :: Database, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 3.2
People
(Reporter: xiaoou.wu, Assigned: xiaoou.wu)
Details
Attachments
(1 file)
977 bytes,
patch
|
mkanat
:
review+
|
Details | Diff | Splinter Review |
Because there are triggers for UPDATE CASCADE, and the normal ' drop table ' will not work for this.
Flags: blocking3.2?
Attachment #344033 -
Flags: review?(mkanat)
Comment 2•17 years ago
|
||
3.2 doesn't drop any tables...well, except if you delete a custom field, I suppose. So I guess this is a blocker indeed, then.
Flags: blocking3.2? → blocking3.2+
Target Milestone: --- → Bugzilla 3.2
Comment 3•17 years ago
|
||
Comment on attachment 344033 [details] [diff] [review]
v1
Okay, did you test this?
Also, aren't there other triggers that you're going to have to drop when you drop the table?
Other triggers will be Okay, because the triggers are on the table, when dropping the table, they will be dropped at the same time.
But when things come to FK, the triggers are on the reference table, which is not the table we drop.
Updated•17 years ago
|
Attachment #344033 -
Flags: review?(mkanat) → review+
Updated•17 years ago
|
Flags: approval3.2+
Flags: approval+
![]() |
||
Comment 6•17 years ago
|
||
tip:
Checking in Bugzilla/DB/Oracle.pm;
/cvsroot/mozilla/webtools/bugzilla/Bugzilla/DB/Oracle.pm,v <-- Oracle.pm
new revision: 1.17; previous revision: 1.16
done
3.2rc1:
Checking in Bugzilla/DB/Oracle.pm;
/cvsroot/mozilla/webtools/bugzilla/Bugzilla/DB/Oracle.pm,v <-- Oracle.pm
new revision: 1.6.2.8; previous revision: 1.6.2.7
done
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•