#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: Normal | Resolution: Keywords: | Triage Stage: Accepted Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+------------------------------------- Changes (by Natalia Bidart):
* severity: Release blocker => Normal Comment: For what is worth, the test_json_field_json_null_value as presented in the proposed branch fails in 5.1.x, 4.2.x, 4.1.x, 4.0.x and 3.2.x, so unclear this is truly a release blocker for 5.2.x. Adam, could you provide more details about your bisect outcome? -- Ticket URL: <https://code.djangoproject.com/ticket/36419#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 django-updates+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/django-updates/010701974183e45c-ab85e058-7999-4006-a9d7-f9924b6cbc36-000000%40eu-central-1.amazonses.com.