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
for sense_translation in old_sense.senseTranslations.all():
# iterate over a list because the objects will be removed
for translation in sense_translation.translations.all():
sense_translation.translations.remove(translation)
Are these calls to remove(...) necessary here given that they concern either vanilla many-to-many relationships or a through-model have ForeignKey fields with on_delete=models.CASCADE, e.g. GlossSense?
If the removes are not necessary, could all calls to delete of individual objects, be replaced to the delete of a few querysets? Or even one queryset, if the on_delete=models.CASCADE does the rest?
Has this code actually deleted the object, or merely removed it from the table?
There is some discrepancy between accounts online of
creating and object using the constructor
inserting a row into a table
When said object is deleted, is it actually deleted or just removed from the table?
Normally, an object may not have been deleted if other objects still refer to it
Senses can be shared.
The text was updated successfully, but these errors were encountered:
ADD MORE DESCRIPTION TO CLARIFY WHAT THIS IS ABOUT
THE FOLLOWING IS A CODE SNIPPET BUT IS INSUFFICIENT
@vanlummelhuizen
Has this code actually deleted the object, or merely removed it from the table?
There is some discrepancy between accounts online of
creating and object using the constructor
inserting a row into a table
When said object is deleted, is it actually deleted or just removed from the table?
Normally, an object may not have been deleted if other objects still refer to it
Senses can be shared.
The text was updated successfully, but these errors were encountered: