#20897: Asymmetrical cursor creation in django.db.backeds.BaseDatabaseWrapper
-------------------------------------+-------------------------------------
     Reporter:  emil.filipov@…       |                    Owner:  nobody
         Type:                       |                   Status:  closed
  Cleanup/optimization               |                  Version:  1.5
    Component:  Database layer       |               Resolution:  fixed
  (models, ORM)                      |             Triage Stage:  Accepted
     Severity:  Normal               |      Needs documentation:  0
     Keywords:                       |  Patch needs improvement:  0
    Has patch:  1                    |                    UI/UX:  0
  Needs tests:  0                    |
Easy pickings:  0                    |
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"27aa85246a218b0999c7c9d227eed2afb08ed510"]:
 {{{
 #!CommitTicketReference repository=""
 revision="27aa85246a218b0999c7c9d227eed2afb08ed510"
 Fixed #20897 -- Added make_cursor() for consistent cursor creation

 In django.db.backends.BaseDatabaseWrapper, pulled the creation of
 cursors in the non-debug case into a separate method, in order to
 make behavior more consistent when overriding the cursor creation
 in derived classes.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/20897#comment:3>
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/085.084d94b73f6f291ed5dd6d5b971a267c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to