Closed
Bug 373286
Opened 19 years ago
Closed 19 years ago
Versions from 2.17.4 - 2.23.2 can no longer upgrade
Categories
(Bugzilla :: Installation & Upgrading, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 3.2
People
(Reporter: mkanat, Assigned: mkanat)
References
Details
Attachments
(1 file)
|
1.89 KB,
patch
|
mkanat
:
review+
|
Details | Diff | Splinter Review |
Right now the checksetup tinderbox is burning. Here's why:
* We convert the bugs table to InnoDB.
* The bugs table has a fulltext index on it.
Oh, that doesn't work! But we really don't drop the FULLTEXT index until much later.
We can't use bz_drop_index to remove the index, because we don't have a bz_schema yet. We can't move the InnoDB upgrades, because that could break table creation (beacuse we'd be creating FOREIGN KEY statements against MyISAM tables, and those would just be silently ignored).
The solution is to use bz_drop_index_raw before the InnoDB upgrade, and do the bz_schema updates after the upgrade, if necessary.
I didn't want to do this as just a "checkin fix" because the fix is slightly complicated.
| Assignee | ||
Comment 1•19 years ago
|
||
Okay, this fixes it fairly well. It also prevents people from having to rename the short_desc fulltext index, which can be pretty huge, so that's an added bonus. :-)
| Assignee | ||
Comment 2•19 years ago
|
||
Checking in Bugzilla/DB/Mysql.pm;
/cvsroot/mozilla/webtools/bugzilla/Bugzilla/DB/Mysql.pm,v <-- Mysql.pm
new revision: 1.51; previous revision: 1.50
done
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Flags: approval+
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•