#36419: bulk_update() incorrectly updates JSONField None to JSON 'null' instead
of
SQL NULL
-------------------------------------+-------------------------------------
Reporter: Clifford Gama | Owner: Clifford
| Gama
Type: Bug | Status: assigned
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Adam Johnson):
Adam, could you provide more details about your bisect outcome?
I bisected for my client project failure, so unfortunately, I can't really
share that. I found that the client test failed for
e306687a3a5507d59365ba9bf545010e5fd4b2a8.
I then minimized the issue into the test provided in
https://github.com/django/django/pull/19527 , which reproduces the
exception I encountered. I didn't bisect with that test before.
I just tried bisecting with it and found
1df0f998ae8d1626adaa9b807a43e4cbdfc590e2, the 5.2 backport of
00c690efbc0b10f67924687f24a7b30397bf47d9, is indeed the first commit that
makes my test fail.
So it seems we're working on the same issue, but it may be that there may
be some other failure lurking in the client project test. I'll try to
check, but no promises!
--
Ticket URL: <https://code.djangoproject.com/ticket/36419#comment:9>
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/0107019741df03b3-4787f3b2-18e7-4d84-a097-3605568f4cf0-000000%40eu-central-1.amazonses.com.
