#4714: JSON serializer doesn't handle None primary keys correctly (has tests.)
--------------------------------------------------------+-------------------
Reporter: [EMAIL PROTECTED] | Owner:
pigletto
Status: assigned | Component:
Serialization
Version: SVN | Resolution:
Keywords: json serialization primary key None null | Stage:
Ready for checkin
Has_patch: 1 | Needs_docs:
0
Needs_tests: 0 | Needs_better_patch:
0
--------------------------------------------------------+-------------------
Changes (by pigletto):
* has_patch: 0 => 1
* stage: Accepted => Ready for checkin
Comment:
Patch contains tests but tests won't fail only if
http://code.djangoproject.com/ticket/5448 is already checked in.
In other words, tests from this ticket are dependent of fix from 5448.
Original ticket was only about primary keys issue but I've found that
there were some more unconsistences in serializer code.
In general 'pk' was always converted to unicode while primary keys from
related fields were taken as is.
I've changed this behaviour that now every string is converted to unicode,
while other types stay as they are.
One big deal with this path is that in some cases backward compatiblity
may be broken!
It is because now, if you have number in primary key, it will be
serialized as a number (in JSON: 'pk: 1). Previously it was always
'pk':"1".
--
Ticket URL: <http://code.djangoproject.com/ticket/4714#comment:3>
Django Code <http://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 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
