#21205: related_objects() fails on SQLite when passing more than 999 objects
-------------------------------------+-------------------------------------
Reporter: NiGhTTraX | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: sqlite delete | Unreviewed
related 999 | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by NiGhTTraX):
Seems like it. But, looking at the proposed patch, I see that it doesn't
use the max_batch_size database ops.
Also, the splitting occurs at the collect() level, while I propose that it
happens in related_objects(), as that's where the problem lies.
Feel free to discuss both patches.
I think this should be fixed as soon as possible since it could break a
lot of people's code, especially when trying to truncate tables via
objects.all().delete().
--
Ticket URL: <https://code.djangoproject.com/ticket/21205#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 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/067.ccd523ecd682e170a16cd3d96afcbad5%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
