[k] Schema migrations are out of sync with reality

RESOLVED FIXED in 2.1

Status

P1
blocker
RESOLVED FIXED
9 years ago
9 years ago

People

(Reporter: jsocol, Assigned: jsocol)

Tracking

unspecified

Firefox Tracking Flags

(Not tracked)

Details

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

(Assignee)

Description

9 years ago
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.
(Assignee)

Comment 2

9 years ago
http://github.com/jsocol/kitsune/commit/572ed80ae
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.