It isn't necessary to disable set_autocommit since its use is prohibited
inside an atomic block. It's still necessary to disable the legacy
transaction management methods for backwards compatibility, until
they're removed.

Since unmanaged == autocommit, there's nothing to commit or roll back.

There isn't much else to say, really.

Apparently django.db.transaction used to be an object.

Replaced them with per-database options, for proper multi-db support.

Also toned down the recommendation to tie transactions to HTTP requests.
Thanks Jeremy for sharing his experience.

It disables transaction management entirely when AUTOCOMMIT is False.

Thanks Florian again.

Currently it only works in autocommit mode.

Based on @xact by Christophe Pettus.

Technically speaking they aren't usable yet.

Prepared for using savepoints within transactions in autocommit mode.

These methods are only called when uses_savepoints = True anyway.

It's synchronized with the autocommit flag.

Since "unless managed" now means "if database-level autocommit",
committing or rolling back doesn't have any effect.

Restored transactional integrity in a few places that relied on
automatically-started transactions with a transitory API.

This is mostly a documentation change.

It has the same backwards-incompatibility consequences as those
described for PostgreSQL in a previous commit.

The goal is to make all databases share a common, autocommit-based,
implementation.

This API is useful because autocommit cannot be managed without an open
connection.

For users who didn't activate autocommit in their database options, this
is backwards-incompatible in "non-managed" aka "auto" transaction state.
This state now uses database-level autocommit instead of ORM-level
autocommit.

Also removed the uses_autocommit feature which lost its purpose.

Autocommit cannot be manipulated independently from an open connection.
This commit introduces a minor change in behavior: entering transaction
management forces opening a databasse connection. This shouldn't be
backwards incompatible in any practical use case.

enter_transaction_management() was nearly always followed by managed().

In three places it wasn't, but they will all be refactored eventually.
The "forced" keyword argument avoids introducing behavior changes until
then.

This is mostly backwards-compatible, except, of course, for managed
itself. There's a minor difference in _enter_transaction_management:
the top self.transaction_state now contains the new 'managed' state
rather than the previous one. Django doesn't access
self.transaction_state in _enter_transaction_management.

Obviously it isn't set until the URL is resolved.

Refs #19584.

Fixed #20018: Added backtick to fix reference

Fixed #20018

Thanks senden9 at gmail.com for the report.

Thanks reidpr at lanl.gov for the report.