#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 cardonbj):
I agree with getting this fixed, and hopefully in an incremental to 1.4.
My company *will not* migrate to Django 1.4 unless the test suite passes
on SQLite (which we use for trunk development), which it currently does
not. I have a very hard time believing that this is not relatively common
among Django dev houses as sqlite is the simplest way to get your
application going without worrying about setting up and configuring a more
reliable database.
--
Ticket URL: <https://code.djangoproject.com/ticket/17788#comment:38>
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.
