#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: 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 akaariai):
I don't think we are going to have a default on MySQL. The reason is it is
pretty much impossible to guess the correct batch size (2 objects might be
too much). However, we could expose a batch_size parameter, and suggest
users set that to something reasonably low.
In addition, can we __please__ fix the SQLite "too many variables" error?
That one hits me 9/10 of times when doing database performance testing. Is
there opposition to adding batch_size parameter to bulk_create which
defaults to unlimited, except for sqlite the default is set so that the
variable limit is not hit. Yes, there could be problems for self-
referential foreign keys. But that query is already doomed, as this would
just trade "too many variables" to "foreign key broken" on the rare case
there is actually a problem.
--
Ticket URL: <https://code.djangoproject.com/ticket/17788#comment:35>
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.
