#23758: Going beyond 5 levels of subqueries causes AssertionError in bump_prefix
-------------------------------------+-------------------------------------
     Reporter:  richardhowardsparx   |                    Owner:
                                     |  piotrpawlaczek
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  1.7
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  fixed
     Keywords:  bump_prefix          |             Triage Stage:  Ready for
  subquery alias                     |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Tim Graham <timograham@…>):

 In [changeset:"e11ff3975f69b96521d94417bbe4125f4abb2774"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e11ff3975f69b96521d94417bbe4125f4abb2774"
 [1.7.x] Fixed #23758 -- Allowed more than 5 levels of subqueries

 Refactored bump_prefix() to avoid infinite loop and allow more than
 than 5 subquires by extending the alphabet to use multi-letters.

 Backport of 41fc1c0b5eac156e200a10233c7c9210a1c0fed8 from master
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/23758#comment:12>
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 post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/076.e1880131521ba60f6684f4037fac055f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to