Re: [Django] #33647: bulk_update and bulk_create silently truncating values for size limited fields on postgres

[Django]

#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 Rowan Douglas):

Thank you for the suggestions. I will make sure to go over the history of
this ticket and the related tickets you mentioned before starting.

As a new contributor, I would like to clarify the backport reasoning. Am I
correct in understanding that changing the signature of Field.db_type is
only something that can occur on the active branch as it is not purely a
fix, but also a change in the general interface. Therefore we will make a
specific fix for the stable branches first, and then introduce the bigger
change as part of the next release.

Let me know if I have misunderstood anything.
--
Ticket URL: <https://code.djangoproject.com/ticket/33647#comment:30>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#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]

#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):

Hi Rowan, just a heads up that we're targeting a patch release fixing 6.0
regressions on January 6. I'm likely to assign this to myself around Dec
30 or so if there's not a PR yet. Just wanted to over-communicate with the
holidays approaching. Thanks again.
--
Ticket URL: <https://code.djangoproject.com/ticket/33647#comment:32>