686160 - Update scripts/schema.sql

Status: RESOLVED FIXED

(support.mozilla.org :: General, defect, P3)

Description

[James Socol [:jsocol, :james]]

We should update scripts/schema.sql and wipe out old migrations again. There are a number of things that need to be added to, and removed from, schema.sql.

Comment 1

[Will Kahn-Greene [:willkg] ET needinfo? me]

This is the can that keeps getting kicked, but fixing it makes life easier for contributors and new developers.

I have no idea what this entails, though. Can someone who's done it before walk through the steps?

Comment 2

[Ricky Rosario [:rrosario, :r1cky]]

I haven't done this before, but the steps should be something like:

1- Get a fresh db dump from production.
2- Export(?) the schema to scripts/schema.sql
3- Remove all of the migrations/*.sql
4- Commit to repo

I am not sure about the details of step 2, but I assume that is straightforward.

Comment 3

[James Socol [:jsocol, :james]]

You don't want any of the production data, but several of the Django tables should be non-empty.

This is what I did:

1) Create a new database.
2) Load scripts/schema.sql.
3) Run schematic.
4) mysqldump back to scripts/schema.sql.
5) Remove the migrations/*sql files, or at least most of them.

An alternative would be to syncdb with a new database, then mysqldump the output of that. That *should* be the same**. Double check table engine and charset/collation, though.

** Well, technically it won't, because we never added migrations for the djcelery tables. Which we should do. But we can just add those with CREATE TABLE IF NOT EXISTS and should be fine.

Comment 4

[Ricky Rosario [:rrosario, :r1cky]]

https://github.com/mozilla/kitsune/commit/ce788faa3f070e82f48e67babfd90e7ce6274171