save() behavior when updating model with default primary keys

Using Django Using the ORM
4

I found the section in the docs at Model instance reference | Django documentation | Django that I think covers this.

The one gotcha here is that you should be careful not to specify a primary-key value explicitly when saving new objects, if you cannot guarantee the primary-key value is unused. For more on this nuance, see Explicitly specifying auto-primary-key values above and Forcing an INSERT or UPDATE below.

So apparently this is expected behavior, and as such, I’m moving this thread back to the “Using Django” bucket.