#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 Claude Paroz):
Replying to [comment:19 Marti Raudsepp]:
> * Fork Django, backport the fix manually, and continue to maintain the
fork until Django 3.1.0 is released and upgrading is viable
I think that's clearly the way to go if the fix is critical to your
application. You may have to update your fork once a month if Django
periodic minor release contains security fixes, but that's a price to pay
for Django general stability where you can almost blindly apply minor
upgrades without worrying. And even with this strict backport policy, it
has happened in the past that such fixes have introduced regressions, so I
don't think we should relax this policy.
--
Ticket URL: <https://code.djangoproject.com/ticket/31301#comment:21>
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.e543bb21535c1c911f8124fd6b36768b%40djangoproject.com.
