|
@@ -0,0 +1,40 @@
|
|
|
+# -*- coding: utf-8 -*-
|
|
|
+from __future__ import unicode_literals
|
|
|
+
|
|
|
+from django.db import migrations, models
|
|
|
+
|
|
|
+
|
|
|
+class Migration(migrations.Migration):
|
|
|
+ # This flag is used to mark that a migration shouldn't be automatically run in
|
|
|
+ # production. We set this to True for operations that we think are risky and want
|
|
|
+ # someone from ops to run manually and monitor.
|
|
|
+ # General advice is that if in doubt, mark your migration as `is_dangerous`.
|
|
|
+ # Some things you should always mark as dangerous:
|
|
|
+ # - Adding indexes to large tables. These indexes should be created concurrently,
|
|
|
+ # unfortunately we can't run migrations outside of a transaction until Django
|
|
|
+ # 1.10. So until then these should be run manually.
|
|
|
+ # - Large data migrations. Typically we want these to be run manually by ops so that
|
|
|
+ # they can be monitored. Since data migrations will now hold a transaction open
|
|
|
+ # this is even more important.
|
|
|
+ # - Adding columns to highly active tables, even ones that are NULL.
|
|
|
+ is_dangerous = False
|
|
|
+
|
|
|
+ dependencies = [
|
|
|
+ ('sentry', '0011_remove_pagerdutyservice_service_id_from_state'),
|
|
|
+ ]
|
|
|
+
|
|
|
+ operations = [
|
|
|
+ migrations.SeparateDatabaseAndState(
|
|
|
+ database_operations=[
|
|
|
+ migrations.RunSQL(
|
|
|
+ """
|
|
|
+ ALTER TABLE "sentry_pagerdutyservice" DROP COLUMN "service_id";
|
|
|
+ """,
|
|
|
+ reverse_sql="""
|
|
|
+ ALTER TABLE "sentry_pagerdutyservice" ADD COLUMN "service_id" varchar(255) NULL;
|
|
|
+ """,
|
|
|
+ )
|
|
|
+ ],
|
|
|
+ state_operations=[],
|
|
|
+ )
|
|
|
+ ]
|