#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):
OK, so it seems safe to say Oracle doesn't suffer from this. You need 64K
of SQL string without the parameters, and that will fit a lot of
placeholders. I checked DB2 and `SqlServer` and they seems to be safe
enough from this issue, too.
So, it seems the only problematic backend is SQLite with its 1000
parameters limit. Fixing bulk_create is not that hard, but I have no idea
how hard it is to fix delete. If delete is hard, is it worth fixing
bulk_create alone? If both are somewhat easy then I think this should be
done. It will make testing a little bit easier. If this is fixed, there is
at least one 2500 object creating test in queries which should be fixed,
too. Makes the test runner a few seconds faster.
--
Ticket URL: <https://code.djangoproject.com/ticket/17788#comment:16>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
