Re: [Django] #4656: Allow In-depth serialization by specifying depth to follow relationship
Django
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
jay.m.martin@… | Status: new
Type: New | Component: Core
feature | (Serialization)
Milestone: | Severity: Normal
Version: | Keywords: feature
Resolution: | Has patch: 0
Triage Stage: Accepted | Needs tests: 0
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by guettli):
* cc: hv@… (added)
* ui_ux: => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/4656#comment:28>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
jay.m.martin@… | Status: new
Type: New | Component: Core
feature | (Serialization)
Milestone: | Severity: Normal
Version: | Keywords: feature
Resolution: | Has patch: 0
Triage Stage: Accepted | Needs tests: 0
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Comment (by tomchristie):
There is some movement on this ATM.
I sprinted on the task at !DjangoCon.eu and made some progress, which Russ
broadly gave a thumbs up to.
If anyone's interested in helping out and finally making some progress on
this it'd be great if you could get in touch.
I've emailed the dev list with a rough proposal as it stands, and there's
an initial implementation, see here...
https://groups.google.com/d/topic/django-developers/H2EKZBsRlFY/discussion
There's certainly more work to do in terms of making sure the interface is
something we'll be happy with, that ties in nicely with the exiting Forms
API style, and with dealing with both serialization and de-serialization,
but I think what we have now looks about right. (Positive criticisms are
very welcomed of course.)
Prob. best to take any further discussion to the dev list.
--
Ticket URL: <https://code.djangoproject.com/ticket/4656#comment:29>
Django
Reporter: jay.m.martin@… | Owner: nobody
Type: New feature | Status: new
Component: Core (Serialization) | Version:
Severity: Normal | Resolution:
Keywords: feature | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by anonymous):
* needs_better_patch: 0 => 1
Comment:
This implementation does quite a lot queries that can be easily saved!
Why can't you just change the implementation of the serializers to follow
the fields retrieved using the 'select_related' method?
Then you can also follow django's already existing conventions and allow
the 'fields' property to accept values like: "related_model__field1" like
in the 'filter' method?
--
Ticket URL: <https://code.djangoproject.com/ticket/4656#comment:30>
Django
--------------------------------------+------------------------------------
Reporter: jay.m.martin@… | Owner: nobody
Component: Core (Serialization) | Version:
Severity: Normal | Resolution: wontfix
Keywords: feature | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
* status: new => closed
* resolution: => wontfix
Comment:
Unless theres a more fundamental addressing of the serialization API,
aimed at making it *generally* usable and extendable for Web APIs I don't
see any value in pushing the scope of the serializers as they now stand.
Right now the use case for them should be for fixture loading and saving
and nothing else. There are better tools out there for generally
extendable serialization schemes (REST framework, tastypie, etc).
Could we address tickets like this? Sure, but not until and unless we're
doing that in the context of a fully fledged serializer API that's
properly suitable for meeting the use cases of both Web APIs *and* fixture
generation.
--
Ticket URL: <https://code.djangoproject.com/ticket/4656#comment:31>