Michael,
I've been able to reproduce it: I'm not quite sure of the best way to deal
with it.
One solution is to set either null=True, or blank=True on the field, or set
a default.
The trick is, an empty string isn't valid JSON. I guess I've always been
using a default (usually of {} or [], depending upon context).
Happy for you to suggest improvements, though.
I believe it's actually related
to
https://bitbucket.org/schinckel/django-jsonfield/issue/13/integrityerrors-when-using-empty-string
Matt.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-users/-/tymGeL-UuCgJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
