#19154: TransactionManagementError raised when data is not changed
--------------------------------------+------------------------------------
Reporter: als | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.4
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by claudep):
* needs_better_patch: => 0
* component: Uncategorized => Documentation
* needs_tests: => 0
* needs_docs: => 0
* type: Uncategorized => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
Yes, this is intended behaviour and the documentation should be updated.
The behaviour is explicitely tested (see transactions_regress tests). You
can read lengthy related discussions on #9964. It is not possible for
Django to really know if data have been modified or not, as SELECT-only
statements can modify data.
--
Ticket URL: <https://code.djangoproject.com/ticket/19154#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
