#31423: Transactions documentation error
-------------------------------------+-------------------------------------
Reporter: AxeOfMen | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 3.0
Severity: Normal | Resolution:
Keywords: documentation | Triage Stage:
transaction atomic | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
I think usage of both is a view decorator and a context manager is
intentional
> In this example, even if `generate_relationships()` causes a database
error by breaking an integrity constraint, you can execute queries in
`add_children()`, and the changes from `create_parent()` are still there.
Maybe the text could be augmented with ''... are still there and are part
of the same transaction.'' to denote that either both changes would be
committed or rolled back.
--
Ticket URL: <https://code.djangoproject.com/ticket/31423#comment:2>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.5ad2845668512ed7962daef0c0d06735%40djangoproject.com.
