#31301: bulk_create with ForeignKey fields with mixed filled/None values fails.
-------------------------------------+-------------------------------------
Reporter: Hans Aarne Liblik | Owner: Hans
| Aarne Liblik
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: oracle sql | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Marti Raudsepp):
What's your suggested solution for users who are hitting this bug now? I
can think of:
* Fork Django, backport the fix manually, and continue to maintain the
fork until Django 3.1.0 is released
* Upgrade to Django development "master" branch, which sometimes breaks
third-party Django addons
* Stop using Django until August 2020 rolls around (just sarcastic,
sorry!)
Am I missing something? This is behavior that everyone agrees is a bug,
and a helpful user provided pull request to fix it. Yet you are leaving
users hanging without a good solution for ~5 months.
Seems like a bug in the backport policy itself :)
--
Ticket URL: <https://code.djangoproject.com/ticket/31301#comment:19>
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.1e4ed5710978144f18cc8b24fc111787%40djangoproject.com.
