I'm using both django-pgtrigger and django-syzygy in my current main project. Both great packages 😄
django-syzygy is a package to make migrations safe during deployments.
Both packages patch MigrationAutodetector independently. syzygy imports Django's original class at module import time (before pgtrigger patches it), so pgtrigger's mixin never ends up in the MRO. Trigger operations are silently dropped. Workaround is not super complicated with syzygy's --dsiable-syzygy, but still annyoing and easy to miss.
I'm currently not sure whether it's better to adjust pgtrigger or django-syzygy, but I'll look into it, just wanted to get this out of the door.
I'm using both django-pgtrigger and django-syzygy in my current main project. Both great packages 😄
django-syzygy is a package to make migrations safe during deployments.
Both packages patch
MigrationAutodetectorindependently. syzygy imports Django's original class at module import time (before pgtrigger patches it), so pgtrigger's mixin never ends up in the MRO. Trigger operations are silently dropped. Workaround is not super complicated with syzygy's--dsiable-syzygy, but still annyoing and easy to miss.I'm currently not sure whether it's better to adjust pgtrigger or django-syzygy, but I'll look into it, just wanted to get this out of the door.