#21134: Documentation for transaction.atomic needs more explicit warning about
catching DatabaseErrors
-------------------------------------+-------------------------------------
     Reporter:  RichardOfWard        |                    Owner:  aaugustin
         Type:                       |                   Status:  assigned
  Cleanup/optimization               |                  Version:
    Component:  Database layer       |  1.6-beta-1
  (models, ORM)                      |               Resolution:
     Severity:  Normal               |             Triage Stage:  Accepted
     Keywords:                       |      Needs documentation:  0
    Has patch:  0                    |  Patch needs improvement:  0
  Needs tests:  0                    |                    UI/UX:  0
Easy pickings:  0                    |
-------------------------------------+-------------------------------------
Changes (by aaugustin):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * component:  Documentation => Database layer (models, ORM)
 * needs_tests:   => 0
 * version:  1.5 => 1.6-beta-1
 * owner:  nobody => aaugustin
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 I added a warning to the docs earlier today, see [4db2752e] and
 [0ad178c4].

 Anssi also suggested that Django should raise an error when attempting to
 make database queries while a broken transaction is in progress. This
 would improve cross-database consistency, normalizing to PostgreSQL's
 behavior.

 Here's a patch implementing this idea:
 
https://github.com/RichardOfWard/django/commit/cb46c75db275db59b54511c090286255bd9cc46d

 Full discussion: https://groups.google.com/d/topic/django-developers
 /ACLQRF-71s8/discussion

-- 
Ticket URL: <https://code.djangoproject.com/ticket/21134#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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.e9245bfef586d0eaa617b5f15433f7c3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to