> If we have a separate API call will it solve the problem with the signals? I suspect not, but asking anyway :)
Actually, funny that you should mention this because Jeroen and I have been having the exact same thought:
If we save the object using obj.save() then the signals will be fired… but if we use update() then we're good because update() doesn't call the signals.
https://docs.djangoproject.com/en/dev/topics/db/queries/#updating-multiple-objects-at-once
"""
Be aware that the update() method is converted directly to an SQL statement. It is a bulk operation for direct updates. It doesn’t run any save() methods on your models, or emit the pre_save or post_save signals (which are a consequence of calling save()), or honor the auto_now field option.
"""
> If we have a separate API call will it solve the problem with the signals? I suspect not, but asking anyway :)
Actually, funny that you should mention this because Jeroen and I have been having the exact same thought:
If we save the object using obj.save() then the signals will be fired… but if we use update() then we're good because update() doesn't call the signals.
https:/ /docs.djangopro ject.com/ en/dev/ topics/ db/queries/ #updating- multiple- objects- at-once
"""
Be aware that the update() method is converted directly to an SQL statement. It is a bulk operation for direct updates. It doesn’t run any save() methods on your models, or emit the pre_save or post_save signals (which are a consequence of calling save()), or honor the auto_now field option.
"""