#17788: bulk_create() "too many SQL variables" error
-------------------------------------+-------------------------------------
Reporter: alpar | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version:
(models, ORM) | 1.4-beta-1
Severity: Release blocker | 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 carljm):
There is already a `supports_1000_query_parameters` db backend feature,
set to `False` for SQLite and `True` for all other backends. That seems
kind of odd, like it should be `max_query_parameters = 1000` instead, but
it was probably done that way so it could be used with
`skipUnlessDBFeature` in the tests, which is the only place its currently
used.
Whether we leave that feature as it is or change it to a number, it could
be used to resolve both this and #16426. Though if SQLite is really the
only affected backend, it's awfully tempting to just say "get a better
database" rather than introducing a bunch of extra chunking complexity in
both deletion and bulk insertion, just for SQLite's sake.
--
Ticket URL: <https://code.djangoproject.com/ticket/17788#comment:14>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
