Closed Bug 570639 Opened 16 years ago Closed 16 years ago

[k] Schema migrations are out of sync with reality

Categories

(support.mozilla.org :: Knowledge Base Software, task, P1)

Product:
support.mozilla.org
Component:
Knowledge Base Software
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jsocol, Assigned: jsocol)

Details

(Whiteboard: [qa-][code quality])

Running the migrations on a fresh dump from production, I ran into the following issues: * Several tables were MyISAM, not InnoDB as they should have been. (In the future we need to be explicit on all our CREATE TABLE statements.) * The is_sticky column/index already exists. (Migration 1) * A foreign key is missing (probably because of the MyISAM/InnoDB issue). (Migration 7) We should make these Just Work™ on production. Patch incoming.
http://github.com/jsocol/kitsune/commit/572ed80ae
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.