Same logic than #158: in Django, validation doesn't belong to Model.save(). It also results in less code, more is delegated to django itself. Less code on our side is less bugs and less maintenance.
Also, in case of bulk update, the custom save method is not called.
For real model-level validity guarantee, we should use database constraints (but they come with their caveats: it more robust than django validation but it's also significantly more constraints once they are in place).
Same logic than #158: in Django, validation doesn't belong to
Model.save(). It also results in less code, more is delegated to django itself. Less code on our side is less bugs and less maintenance.Also, in case of bulk update, the custom
savemethod is not called.For real model-level validity guarantee, we should use database constraints (but they come with their caveats: it more robust than django validation but it's also significantly more constraints once they are in place).