#33647: bulk_update and bulk_create silently truncating values for size limited
fields on postgres
-------------------------------------+-------------------------------------
Reporter: jerch | Owner: Rowan
| Douglas
Type: Bug | Status: assigned
Component: Database layer | Version: 4.0
(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 Jacob Walls):
In principle that's right, but all contributions go through main, and
mergers will handle any backports, so just target `main`.
We really only need to repair 6.0 and 5.2 to the state before the `UNNEST`
strategy replicated this old issue inside `bulk_create`. Then the
`parameterized=False` bit to clean up that planned Postgres `bulk_create`
fix and finally fix `bulk_update` would not get backported, so make sure
that work is in a separate commit.
--
Ticket URL: <https://code.djangoproject.com/ticket/33647#comment:31>
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/0107019b0a5dd6a4-f82cc95d-bbb8-4708-9534-edb944b3f455-000000%40eu-central-1.amazonses.com.
