#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 akaariai):
I am going to test if Oracle has any batch size limits.
For PostgreSQL there is no practical limit. I tested this and once you go
to millions of objects you could OOM your server, but most likely you will
OOM your Python process before that.
For what I know MySQL does not have any practical limit either. 16Mb of
query string should be enough for everybody(tm).
Oracle is an open question, and then there are all the third party
databases. It would maybe be worth to have an API of
get_next_batch(param_count, params). For example sqlite could return
min(1000/param_count, len(params)/param_count).
--
Ticket URL: <https://code.djangoproject.com/ticket/17788#comment:9>
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.
