database: add database migration file that replaces Django fixtures

We used to rely on a Django fixtures to add a single record of initial data to the afe_acl_groups table. We can simply move that data to the schema, or, as done here, in a database version migration script. This fixes issue autotest#503. Signed-off-by: Cleber Rosa <[email protected]>
yumingfei · Aug 30, 2012 · b7c9de0 · b7c9de0
1 parent bf0acde
commit b7c9de0
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 1 deletion.
diff --git a/frontend/afe/fixtures/initial_data.json b/frontend/afe/fixtures/initial_data.json
diff --git a/frontend/migrations/070_add_acl_group_replace_django_fixture.py b/frontend/migrations/070_add_acl_group_replace_django_fixture.py
@@ -0,0 +1,8 @@
+UP_SQL = """
+INSERT INTO afe_acl_groups (id, name) VALUES (1, 'Everyone') ON DUPLICATE KEY UPDATE name='Everyone';
+"""
+
+# Since this used to be a value INSERTED by Django fixtures, do not remove it
+# when downgrading versions
+DOWN_SQL = """
+"""