The difference between save and save_model ()

Question

For all my Django tasks that require overriding the save method, I used save() in my models. Suddenly, when I was looking for something that required a bit of extra flash, someone suggested overriding save_model() in my admin class.

I found documents for both, and immediately noticed that the arguments are different. save_model() called only when the administrator saves the model? and the save() method is called whenever the model is saved?

UPDATE

So, I realized that when saving from the administrator. "Save" and "save_model ()" are called. It looks like 'save_model ()' is called first. In my particular application, I use pre_save signals, and "save ()" overrides. Now I want to add overrides to 'save_model ()'. This interaction and the order of all of them preserve overrides and signals that confuse me.

Answer 1

Since save() is a Model method, whereas save_model() is a ModelAdmin method ... yes.