Wes Kendall
Wes Kendall
@dracos very clever for the update case! Yes, you can do three as well and then have a condition on the update to only fire when the entry has been...
@rrauenza yea this is a tricky issue. In the latest version of pgtrigger, it is integrated with the migration system, which should help some of these use cases. Unfortunately I...
@rrauenza just verified that this is a bug even with integration in the migration system. I'm going to follow up on this one next week and try to tackle it...
@rrauenza this is fixed in https://github.com/Opus10/django-pgtrigger/pull/83 To fix this, I patched the schema editor to temporarily drop/recreate the affected triggers when the column type is changed. I made a test...
Note that this fix works with both the migration system and with the legacy way of installing all triggers after migrations.
Version 4.1 is now deployed!
@davecoates thanks so much for bringing this to my attention. I will update the upgrade notes here and in the official docs today. It totally slipped my mind that the...
Added a third bullet point to the migration notes and also updated it in the FAQ in #94
Did you read [this section of the docs](https://django-pgtrigger.readthedocs.io/en/latest/deferrable.html) on how to do this? Or did you try it and receive an error? Deferrable constraint triggers are configured by setting the...
Going to close this since I believe it's been answered. Feel free to re-open you're still having issues