> One reason not to do this is that it simply isn't standard behaviour forI'm not convinced by the argument of least-surprise. As you said,
> Python database adaptors (they must be in non-autocommit mode
> initially). So there's a principle of least-surprise thing going on.
are explicit commit_unless_managed() calls inside the Django internals
(e.g. inside save() ) - but a Django _user_ (rather than developer)
not have read this code before calling save().
So, a Django user who expects Python database adaptors to be
By designing default Django behaviour to be "similar to auto-commit",
It's now a case of how Django implements the "similar to auto-commit"
I suspect that this will significantly simplify the Django codebase
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.