#36502: bulk_create on Postgres doesn't use the unnest strategy when foreign
keys
are involved since 5.2.1
-------------------------------------+-------------------------------------
Reporter: canardoFR | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: postgres | Triage Stage: Ready for
bulk_create unnest foreignkey | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"0fe218842e0e396e3ab3982bd21227968a9e7fd8" 0fe2188]:
{{{#!CommitTicketReference repository=""
revision="0fe218842e0e396e3ab3982bd21227968a9e7fd8"
Fixed #36502 -- Restored UNNEST strategy for foreign key bulk inserts on
PostgreSQL.
Regression in 764af7a3d6c0b543dcf659a2c327f214da768fe4.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36502#comment:6>
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/01070197f52ef400-9f3a9645-92a3-4dea-986f-f8a4906cdeae-000000%40eu-central-1.amazonses.com.
