0190_drop_external_user_table.py 2.0 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344
  1. # Generated by Django 1.11.29 on 2021-05-03 21:05
  2. from django.db import migrations
  3. class Migration(migrations.Migration):
  4. # This flag is used to mark that a migration shouldn't be automatically run in
  5. # production. We set this to True for operations that we think are risky and want
  6. # someone from ops to run manually and monitor.
  7. # General advice is that if in doubt, mark your migration as `is_dangerous`.
  8. # Some things you should always mark as dangerous:
  9. # - Large data migrations. Typically we want these to be run manually by ops so that
  10. # they can be monitored. Since data migrations will now hold a transaction open
  11. # this is even more important.
  12. # - Adding columns to highly active tables, even ones that are NULL.
  13. is_dangerous = False
  14. # This flag is used to decide whether to run this migration in a transaction or not.
  15. # By default we prefer to run in a transaction, but for migrations where you want
  16. # to `CREATE INDEX CONCURRENTLY` this needs to be set to False. Typically you'll
  17. # want to create an index concurrently when adding one to an existing table.
  18. # You'll also usually want to set this to `False` if you're writing a data
  19. # migration, since we don't want the entire migration to run in one long-running
  20. # transaction.
  21. atomic = True
  22. dependencies = [
  23. ("sentry", "0189_remove_externaluser_externalteam_models"),
  24. ]
  25. operations = [
  26. migrations.RunSQL(
  27. """
  28. DROP TABLE "sentry_externaluser";
  29. """,
  30. reverse_sql="CREATE TABLE sentry_externaluser (fake_col int)", # We just create a fake table here so that the DROP will work if we roll back the migration.
  31. ),
  32. migrations.RunSQL(
  33. """
  34. DROP TABLE "sentry_externalteam";
  35. """,
  36. reverse_sql="CREATE TABLE sentry_externalteam (fake_col int)", # We just create a fake table here so that the DROP will work if we roll back the migration.
  37. ),
  38. ]