#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 aaugustin):
Possibly a stupid question, but what if the model has a foreign key to
itself? Isn't the chunking likely to break foreign key constraints?
Even though the patch is rather straightforward, I'm really wary of
unexpected side effets, on the eve of a release candidate.
I suggest we document the problem as a know limitation of the SQLite
backend in 1.4 and fix it properly later -- along with the other problems
triggered by this limitation, like #16426.
--
Ticket URL: <https://code.djangoproject.com/ticket/17788#comment:18>
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.
