#36107: PostgresSQL ArrayField with size crashes with bulk_create
-------------------------------------+-------------------------------------
Reporter: Claude Paroz | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce <42296566+sarahboyce@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"22fc151bb86a553d84c62d7effd289356e9b6c6c" 22fc151b]:
{{{#!CommitTicketReference repository=""
revision="22fc151bb86a553d84c62d7effd289356e9b6c6c"
Fixed #36107 -- Adjusted UNNEST bulk_create strategy to opt-out sized
arrays.
The array fields opt-out heuristic failed to account for sized arrays.
Note that we keep relying on db_type as opposed to performing an
ArrayField
instance check against the column's field as there could be other
implementations of model fields that use Postgres arrays to store the
optimization must be disabled for all of them.
Refs #35936.
Thanks Claude Paroz for the report and test.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36107#comment:5>
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/0107019483dab5da-ca29efcc-8f30-4478-8d3a-8a4f45dc1fe0-000000%40eu-central-1.amazonses.com.
