#24320: Unable to serialize UUIDField when running dumpdata with JSON format
-------------------------------------+-------------------------------------
Reporter: jamesbeith | Owner: coldmind
Type: Bug | Status: closed
Component: Core | Version: 1.8alpha1
(Serialization) |
Severity: Release blocker | Resolution: fixed
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 Tim Graham <timograham@…>):
In [changeset:"136edac8974ff0b570ce0a3e66e7aadf542225f0"]:
{{{
#!CommitTicketReference repository=""
revision="136edac8974ff0b570ce0a3e66e7aadf542225f0"
[1.8.x] Fixed #24320 - Used field.value_to_string() in serialization of
foreign key.
This fixes serialization of a ForeignKey to a UUIDField as the
test indicates.
Backport of 5c995dcfc251b55284e1ef16545acd2acad6be04 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24320#comment:14>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.f8599c347a79d22cd309f110e0165f12%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
