#31301: bulk_create with ForeignKey fields with mixed filled/None values fails
-------------------------------------+-------------------------------------
Reporter: Hans Aarne Liblik | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: oracle sql | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* easy: 0 => 1
* stage: Unreviewed => Accepted
Comment:
That seems like the correct approach. Would you be interested in
submitting a Github PR that addresses the issue?
Based on c4e2fc5d9872c9a0c9c052a2e124f8a9b87de9b4 adding a nullable
foreign key on `NullableFields` to another test model of the same module
should be sufficient to augment the `test_bulk_insert_nullable_fields`
test to cover this case.
--
Ticket URL: <https://code.djangoproject.com/ticket/31301#comment:1>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/073.4ec58573bd32fc9e4a636632301b478c%40djangoproject.com.
