| 90 | 90 | So, at least when I'm in an overwriting posture--and Ken brings up a good point that [https://forum.djangoproject.com/t/save-behavior-when-updating-model-with-default-primary-keys/30778/9 forcing the user to opt in to this potential for data loss] for existing primary keys is worth something--I prefer `save()`. It's simpler and doesn't involve "defaults". (''What's a "default" got to do with updating one row's values?'') It's also faster for the UPDATE case, which is my hot path. I might be in the minority, and could be convinced otherwise. (A third variation is possible, `.filter(pk=known).update(...)`, but not unless you know the objects necessarily exist.) But everything I just said is skating on pretty rarefied ice -- the basic point is that ''huh, I have to be careful with save() depending on the details of my field definitions?'' |