Changes between Initial Version and Version 39 of Ticket #33647


Ignore:
Timestamp:
Dec 31, 2025, 9:51:40 AM (2 weeks ago)
Author:
Jacob Walls
Comment:

Downgrading from release blocker now that we've backported the fix to bulk_create(). Only bulk_update() is still affected (as before). Clarified the ticket description, but leaving both methods in the ticket title so that the reference from the release notes is understandable.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #33647

    • Property Triage Stage Unreviewed → Accepted
    • Property Type Uncategorized → Bug
    • Property Cc Simon Charette Lily added
    • Property Owner changed from nobody to Rowan Douglas
    • Property Status new → assigned
    • Property Summary bulk_update silently truncating values for size limited fields → bulk_update and bulk_create silently truncating values for size limited fields on postgres

  • Ticket #33647 – Description

    initial v39  
     1EDIT: This issue originally only affected `bulk_update`, then started affecting `bulk_create` in Django 5.2, but that aspect was fixed in Django 5.2.10 and Django 6.0.1.
     2
     3Original report follows:
     4
     5----
     6
    17On postgres backend, `bulk_update` passes overlong values for size limited fields along without any notification/exception, instead truncating the value.
    28
Back to Top