#36707: Prefetch related query throwing "Expression tree is too large" error
after
updating to Django 5.2 when using sqlite3 DB
-------------------------------------+-------------------------------------
Reporter: Alexandru Chirila | Owner: (none)
Type: Bug | Status: closed
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Alexandru Chirila):
Replying to [comment:1 Jacob Walls]:
> Thanks for the report. Duplicate of #27833. You may want to update your
sqlite version to take advantage of higher limits as of 3.32.0
Thanks for the reply! I'm already on 3.37, so that doesn't help.
But it does looks like the issue is separate from #27833 because:
a. that issues seems be from 1.10 while this used to work ok, and has been
broken somewhere between 4.2> and <=5.2
b. that issue looks to be about "SQLITE_MAX_VARIABLE_NUMBER", while the
error here is about "SQLITE_MAX_EXPR_DEPTH" which defaults to 1000
--
Ticket URL: <https://code.djangoproject.com/ticket/36707#comment:2>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019a4f518313-0a81fef9-2534-44ed-86c5-2aa4e6a60884-000000%40eu-central-1.amazonses.com.
