#36118: Some usage of bulk_batch_size might not account for composite primary
keys
on SQLite
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Sarah
| Boyce
Type: Bug | Status: assigned
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* stage: Accepted => Ready for checkin
Comment:
After the discussions in the PR which investigated `bulk_batch_size`, we
found:
* The `max_query_params value` used for SQLite is overly protective in
most cases (see ticket #36143)
* There are other factors at play (possibly different settings) than just
the maximum numbers of query parameters that must be considered to have a
complete bullet proof solution (see ticket #36144)
This ticket aims to make sure the current situation (which isn't
perfect/bulletproof) is not worsened by the usage of composite primary
keys.
The solution here has been to have a linear increase (constant time the
number of additional fields in the primary key) of query parameters on
SQLite and Oracle. Further work is captured by the tickets referenced
above.
--
Ticket URL: <https://code.djangoproject.com/ticket/36118#comment:5>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070194b153e479-c9e4e0ae-e2c2-4f28-819a-03e8516becb2-000000%40eu-central-1.amazonses.com.
