paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-11-05 22:43:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

migrations: Disable atomic for delivery_email migration.

Browse Source 
I'm not sure theoretically why this should be required only for some
installations, but these articles all suggest the root problem is
doing these two migrations together atomically (creating the field and
setting a value for it), so the right answer is to declare the
migration as not atomic:

https://stackoverflow.com/questions/12838111/django-db-migrations-cannot-alter-table-because-it-has-pending-trigger-events
https://confluence.atlassian.com/confkb/upgrade-failed-with-the-error-message-error-cannot-alter-table-content-because-it-has-pending-trigger-events-747606853.html
This commit is contained in:
Tim Abbott
2018-09-28 14:09:03 -07:00
parent c91b804683
commit 510afd0c93
1 changed files with 1 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
zerver/migrations/0174_userprofile_delivery_email.py
View File

@@ -15,6 +15,7 @@ def copy_email_field(apps: StateApps, schema_editor: DatabaseSchemaEditor) -> No
class Migration(migrations.Migration): class Migration(migrations.Migration):
atomic = False
dependencies = [ dependencies = [
('zerver', '0173_support_seat_based_plans'), ('zerver', '0173_support_seat_based_plans'),