#23758: Going beyond 5 levels of subqueries causes AssertionError in bump_prefix
-------------------------------------+-------------------------------------
Reporter: Richard Howard | Owner: Piotr
| Pawlaczek
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 Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"0cb40624828f3590ea2460e2e0cf1bd5a2b52496" 0cb4062]:
{{{
#!CommitTicketReference repository=""
revision="0cb40624828f3590ea2460e2e0cf1bd5a2b52496"
Refs #23758 -- Used RecursionError instead of RuntimeError to raise nested
subquery errors.
RecursionError was introduced in Python 3.5 and subclasses RuntimeError.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23758#comment:13>
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/076.842e1a56ce8e0a07f3d486c6e676a94e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
