#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 kmtracey):
Replying to [comment:15 alpar]:
> Replying to [comment:7 carljm]:
> > [...] since it seems likely that the answer "use a better database"
suffices to prevent it being an actual problem in production [...]
>
> My problem is that although we "use a better database" for production,
but we use SQLite during the development, because it is easier to setup,
to create and share snapshots etc.
...and it will quietly accept plenty of error cases that your production
database will choke on, thus hiding errors during development that will
NOT be hidden in production. Get a better database, even in development.
--
Ticket URL: <https://code.djangoproject.com/ticket/17788#comment:26>
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.
