#36118: Some usage of bulk_batch_size might not account for composite primary
keys
on SQLite
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: (none)
Type: Bug | Status: new
Component: Database layer | Version: 5.2
(models, ORM) |
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 Sarah Boyce):
I have been struggling to prove that the "pk" additions in `bulk_update`
are required to prevent an `OperationalError`. See
[https://github.com/django/django/pull/19088 draft PR]
This is also the only case I can find of `bulk_batch_size` with specific
logic for handling primary keys
If we agree these pk additions are not needed, then I think this is no
longer a release blocking bug but rather a cleanup/optimization ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/36118#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701948e49c029-a4384604-566c-4618-ba17-f8ada45307ae-000000%40eu-central-1.amazonses.com.
