You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Imagine this example in Django ORM: myStudent.delete()
If the delete action violated a foreign key constraint, Django will generate an exception (which is correct) but SwampDragon will estimate that the object has been deleted and it will send a false "Object deleted" message to the client that is listening to the channel.
It is not happening when I modify a field and then call myStudent.save(), only happening with delete errors.
Any way to avoid this?
Thanks in advance!
The text was updated successfully, but these errors were encountered:
Hi,
Imagine this example in Django ORM:
myStudent.delete()
If the delete action violated a foreign key constraint, Django will generate an exception (which is correct) but SwampDragon will estimate that the object has been deleted and it will send a false "Object deleted" message to the client that is listening to the channel.
It is not happening when I modify a field and then call myStudent.save(), only happening with delete errors.
Any way to avoid this?
Thanks in advance!
The text was updated successfully, but these errors were encountered: