Just curious as to the best practices for using save/delete in Model versus delete_model/save_model in ModelAdmin. Is one preferred over the other?
In my particular case, I have a Document model with a JSON field that holds a bunch of metadata (name:value pairs) for Documents (photos, pdfs, etc). The metadata is defined in other models (MetaData for names and MetaDataValue for the value(s)), so I can change the metadata names and values at run time. When an existing MetaData name or value changes or is deleted, I need to "scrub" the metadata stored in the Document model to change/delete the metadata names/values to keep them in sync with what is defined in the MetaData and MetaDataValue models. All these changes are done through the Admin screens. Would it be more appropriate to use model_save and model_delete in the Admin or save and delete in the respective models? Functionally, it does not matter as far as I can see. I am just wondering if there is a preferred way, or a more "django idiomatic" way to do this. Thanks! Mark -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAEqej2PGgK%3D%2BEyqrTj3Ds9s8YAOjuW0bB5wYPqedxRFsp9e6zA%40mail.gmail.com.
