#36289: Postgres bulk_create error when geometry is null or a different SRID
-------------------------------------+-------------------------------------
Reporter: Joshua Goodwin | 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
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"d9bf0d07cc13c0351b65b025d7e8063864086975" d9bf0d0]:
{{{#!CommitTicketReference repository=""
revision="d9bf0d07cc13c0351b65b025d7e8063864086975"
[5.2.x] Fixed #36289 -- Fixed bulk_create() crash with nullable geometry
fields on PostGIS.
Swapped to an allow list instead of a deny list for field types to
determine if the UNNEST optimization can be enabled to avoid further
surprises with other types that would require further specialization to
adapt.
Regression in a16eedcf9c69d8a11d94cac1811018c5b996d491.
Thanks Joshua Goodwin for the report and Sarah Boyce for the test.
Backport of 764af7a3d6c0b543dcf659a2c327f214da768fe4 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36289#comment:7>
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/01070196024bf0f4-031dd02c-f450-4329-9d40-3132f1e07010-000000%40eu-central-1.amazonses.com.
