[Django] #12189: Cache database backend should use rollback_unless_managed

View: New views
1 Messages — Rating Filter:   Alert me  

[Django] #12189: Cache database backend should use rollback_unless_managed

by Django-3 :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message

#12189: Cache database backend should use rollback_unless_managed
---------------------------+------------------------------------------------
 Reporter:  lakinwecker    |       Owner:  nobody    
   Status:  new            |   Milestone:            
Component:  Uncategorized  |     Version:  1.1      
 Keywords:                 |       Stage:  Unreviewed
Has_patch:  0              |  
---------------------------+------------------------------------------------
 In 1.1 and trunk I think it would be best if it used
 transaction.rollback_unless_managed() - as this causes an error when the
 code isn't under transaction management:

 source:django/branches/releases/1.1.X/django/core/cache/backends/db.py#L68
 and source:django/trunk/django/core/cache/backends/db.py#L68

--
Ticket URL: <http://code.djangoproject.com/ticket/12189>
Django <http://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 django-updates@...
To unsubscribe from this group, send email to django-updates+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---