Closed jzmiller1 closed 2 years ago
@jzmiller1 I incorrectly sent a message saying this is fixed. Let me investigate further to verify
@jzmiller1 this looks to be postgis specific. I did this change earlier to make it more interoperable with django-postgres-extra and other tools that use custom backends.
Let me see if I can reproduce the error by using a postgis backend in the test suite. There's likely a safer way I can do this.
For now, the way to get around this is to set
PGTRIGGER_SCHEMA_EDITOR = False
in your settings. This suppresses overriding the schema editor. Doing this means that you won't be able to automatically alter column types that are part of trigger conditions (i.e. you will be susceptible to #83 )
I was too quick to patch certain things. I verified this issue with postgis and placed the schema editor patching in App.ready()
. Fix will be deployed shortly
@jzmiller1 fixed in 4.2.1
Thanks for quickly bringing this up!
You're too fast, I didn't get to look for a solution! Thanks for the fix!
After 4.2.0 running pgmakemigrations there errors from the steming from the load_backend call in django-pgtrigger apps.py. I'm running this with PostGIS and django-postres-extras (the same setup as in issue #73 ). I'm not going to have a chance tonight to take a look at resolving it but wanted to share in case others run into similar issues.
Base Model
Error