#3564: flexible JSON serializing mechanism
-----------------------------------+----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: jacob
Status: new | Component: Serialization
Version: SVN | Resolution:
Keywords: | Stage: Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-----------------------------------+----------------------------------------
Comment (by mtredinnick):
I think there's a conceptual problem here: json serialization isn't
something that should be part of a model. It's a presentation data-munging
feature, so it's very much view-layer, rather than intrinsic to the model.
So something like a JSON inner-class in models isn't going to fly.
I'm not completely clear on what problem you are trying to address with
this ticket. Given that you are always going to have to specify which data
to serialise and that will be done most naturally via a queryset, we
currently have it down to a call to something like
{{{serializers.serialize("json", my_queryset)}}}. What situation do you
have where that isn't doing the right thing? A (short) example of where
that gets into trouble and is made easier by your suggestion would
probably help here.
--
Ticket URL: <http://code.djangoproject.com/ticket/3564#comment:2>
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
-~----------~----~----~----~------~----~------~--~---
