File tree Expand file tree Collapse file tree 2 files changed +43
-1
lines changed Expand file tree Collapse file tree 2 files changed +43
-1
lines changed Original file line number Diff line number Diff line change @@ -9,5 +9,5 @@ feedback: 0004_index_together
9
9
hybridcloud: 0016_add_control_cacheversion
10
10
nodestore: 0002_nodestore_no_dictfield
11
11
replays: 0004_index_together
12
- sentry: 0696_remove_monitor_owner_actor_id
12
+ sentry: 0697_remove_monitor_owner_actor_id_db
13
13
social_auth: 0002_default_auto_field
Original file line number Diff line number Diff line change
1
+ # Generated by Django 5.0.3 on 2024-04-12 19:49
2
+
3
+ from django .db import migrations
4
+
5
+ from sentry .new_migrations .migrations import CheckedMigration
6
+
7
+
8
+ class Migration (CheckedMigration ):
9
+ # This flag is used to mark that a migration shouldn't be automatically run in production.
10
+ # This should only be used for operations where it's safe to run the migration after your
11
+ # code has deployed. So this should not be used for most operations that alter the schema
12
+ # of a table.
13
+ # Here are some things that make sense to mark as post deployment:
14
+ # - Large data migrations. Typically we want these to be run manually so that they can be
15
+ # monitored and not block the deploy for a long period of time while they run.
16
+ # - Adding indexes to large tables. Since this can take a long time, we'd generally prefer to
17
+ # run this outside deployments so that we don't block them. Note that while adding an index
18
+ # is a schema change, it's completely safe to run the operation after the code has deployed.
19
+ # Once deployed, run these manually via: https://develop.sentry.dev/database-migrations/#migration-deployment
20
+
21
+ is_post_deployment = False
22
+
23
+ dependencies = [
24
+ ("sentry" , "0696_remove_monitor_owner_actor_id" ),
25
+ ]
26
+
27
+ operations = [
28
+ migrations .SeparateDatabaseAndState (
29
+ database_operations = [
30
+ migrations .RunSQL (
31
+ """
32
+ ALTER TABLE "sentry_monitor" DROP COLUMN "owner_actor_id";
33
+ """ ,
34
+ reverse_sql = """
35
+ ALTER TABLE "sentry_monitor" ADD COLUMN "owner_actor_id" bigint NULL;
36
+ """ ,
37
+ hints = {"tables" : ["sentry_monitor" ]},
38
+ )
39
+ ],
40
+ state_operations = [],
41
+ )
42
+ ]
You can’t perform that action at this time.
0 commit comments