#36445: Value(None, output_field=JSONField()) incorrectly saves as SQL NULL in
bulk_update()
-------------------------------------+-------------------------------------
Reporter: Clifford Gama | Owner: Uddyan
| Goyal
Type: Bug | Status: assigned
Component: Database layer | Version: dev
(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
-------------------------------------+-------------------------------------
Comment (by Clifford Gama):
Replying to [comment:4 Simon Charette]:
> Now that we know this isn't a regression should we consider biting the
bullet and stop trying to make `Value(None, JSONField())` work by
introducing a proper `JSONNull` expression as described in
ticket:35381#comment:3?
In light of recent reports around JSON null/SQL NULL, (the latest being
#36453) I'd say yes. Would this mean marking this ticket as invalid in
favour of a #35381 repurposed for the `JSONNull` new feature?
--
Ticket URL: <https://code.djangoproject.com/ticket/36445#comment:11>
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/01070197658a1238-c4902d87-9b70-4f78-b150-f1f1208408f1-000000%40eu-central-1.amazonses.com.
