clarify behavior of autocommit mode in presence of transaction
|Reported by:||cjerdonek||Owned by:||aaugustin|
|Severity:||Normal||Keywords:||autocommit, transactions, database|
|Cc:||chris.jerdonek@…||Triage Stage:||Ready for checkin|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
As someone relatively new to Django, in reading the Database transactions section of the Django docs, I thought a couple things could be clarified or improved.
Namely, it would be helpful to clarify that both (1) the default "autocommit" behavior of immediately committing doesn't occur if a transaction has already been started, and (2) Django's main TestCase class implicitly starts a transaction (thus "suspending" the default autocommit behavior). Not mentioning the latter in the main transaction docs contributed to my running into documentation issue #21540, so I think resolving this issue will help address issue #21540.
I've already written up a proposed patch with suggested wording for the above. I will post it to this issue shortly. Thanks.
Change History (9)
comment:1 Changed 16 months ago by cjerdonek
- Cc chris.jerdonek@… added
- Needs documentation unset
- Needs tests unset
- Owner changed from nobody to cjerdonek
- Patch needs improvement unset
- Status changed from new to assigned
comment:2 Changed 16 months ago by cjerdonek
- Type changed from Uncategorized to Cleanup/optimization
comment:6 Changed 16 months ago by aaugustin
comment:7 Changed 16 months ago by Aymeric Augustin <aymeric.augustin@…>
- Resolution set to fixed
- Status changed from assigned to closed