#28596: Oracle crashes with id__in query with 100k ids -------------------------------------+------------------------------------- Reporter: Markus Stenberg | Owner: nobody Type: Bug | Status: new Component: Database layer | Version: 1.11 (models, ORM) | Severity: Normal | Resolution: Keywords: | Triage Stage: Accepted Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by Jani Tiainen): I think that Oracle has limitation of 999 (or 1k) entries in a list of a IN query. I recall seeing code that split queries like that to multiple ones in older versions of Django (1.5 and older) but did it worked I can't vouch for. -- Ticket URL: <https://code.djangoproject.com/ticket/28596#comment:6> 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/064.56b6f35aa5d5b925866bf75ef90fbc99%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.