Database commit behavior is confusingly documented

[philipn]

Reading ​https://docs.djangoproject.com/en/dev/ref/databases/:

Transaction handling

By default, Django starts a transaction when a database connection is first used and commits the result at the end of the request/response handling. The PostgreSQL backends normally operate the same as any other Django backend in this respect.

Then reading ​https://docs.djangoproject.com/en/dev/topics/db/transactions/:

Django’s default behavior is to run with an open transaction which it commits automatically when any built-in, data-altering model function is called. For example, if you call model.save() or model.delete(), the change will be committed immediately.

---

​https://docs.djangoproject.com/en/dev/topics/db/transactions/ describes the current behavior. It seems like the other documentation should be updated to reflect this.

[philipn]

It looks like the first case is what happens if you have TransactionMiddleware enabled -- but it's not on by default.

[Anssi Kääriäinen]

True - the PostgreSQL specific documentation isn't correct.

[mateusgondim]

Hi, I replaced the wrong sentence with the right one.

[Tim Graham <timograham@…>]

In [2079b730f139685bcedf0c92d5ed9a3f64b51e9f]:

Fixed #18223 - Corrected default transaction behavior in postgresql docs.

Thanks philipn for the report and mateusgondim for the patch.

[Tim Graham <timograham@…>]

In [01b02317172a5030b77a09aada11657c00398416]:

[1.4.X] Fixed #18223 - Corrected default transaction behavior in postgresql docs.

Thanks philipn for the report and mateusgondim for the patch.

Backport of 2079b730f1 from master