#36248: Bulk deletion of model referred to by a SET_NULL key can exceed
parameter
limit
-------------------------------------+-------------------------------------
Reporter: bobince | Owner: bobince
Type: Bug | Status: assigned
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Thanks for reporting your findings bobince. We are aware that our current
params limiting is far from bullet proof.
The problem
[https://github.com/django/django/pull/19088#discussion_r1925636305 was
recently re-surfaced] when we added support for composite primary key as
they require that the chunk size be divided by the number of fields
included in the relationship.
Some related tickets are #36143, #36144.
> Ugh, I wish param limits would go away
FYI you might be interested to know that SQLite 3.32+
[https://www.sqlite.org/limits.html#max_variable_number seems to default
to a much larger number].
--
Ticket URL: <https://code.djangoproject.com/ticket/36248#comment:7>
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/01070195c131f0a9-d3dad13a-5bbf-49fe-b543-0263a56425c6-000000%40eu-central-1.amazonses.com.
