#36750: dumpdata's output of m2m values is not deterministic
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: VIZZARD-X
Type: Bug | Status: assigned
Component: Core | Version: dev
(Serialization) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Jacob, ordering by the primary key ensures the ordering is total so that
should do if it makes things simpler.
My comment:5 was just to point out to comment:4 that in comment:3 I
suggested using the field referenced by the many-to-many field which is
not necessarily the remote primary key.
The referenced field has to be unique as well and felt like a more
''natural'' default than necessarily picking the primary key but given
this ticket main focus is making sure the output is deterministic primary
is a good choice particularly given the detour we took with
`sql.Query.totally_ordered` (thank you for tha btw).
--
Ticket URL: <https://code.djangoproject.com/ticket/36750#comment:27>
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/0107019c93751e8f-ce72a0c5-0f1d-4ccb-9262-33da2065be27-000000%40eu-central-1.amazonses.com.
