首页
学习
活动
专区
工具
TVP
发布
社区首页 >问答首页 >如何实现资源的层次结构(例如,Django REST框架中的/parents/<id>/children)

如何实现资源的层次结构(例如,Django REST框架中的/parents/<id>/children)
EN

Stack Overflow用户
提问于 2013-06-27 16:05:18
回答 3查看 6.3K关注 0票数 25

我在Django REST Framework网站上的教程中找不到任何关于如何实现这一点的信息,我也没有设法在文档中找到它,尽管我确定它在某个地方。

我希望issues作为父资源,pages作为子资源,这样/issues/1/pages就可以返回issue_id为1的所有页面。

使用基于泛型类的视图有没有实现这一点的好方法?

这是我到目前为止所掌握的。

restAPI/urls.py:

from django.conf.urls import patterns, url
from rest_framework.urlpatterns import format_suffix_patterns
from restAPI import views

urlpatterns = patterns('',
    url(r'^issues/$', views.IssueList.as_view()),
    url(r'^issues/(?P<pk>[0-9]+)/$', views.IssueDetail.as_view()),


    url(r'^issues/(?P<issue_id>[0-9]+)/pages/$', views.PageList.as_view()),    
    url(r'^pages/(?P<pk>[0-9]+)/$', views.PageDetail.as_view()),
)

urlpatterns = format_suffix_patterns(urlpatterns)

restAPI/models.py:

from django.db import models

class Issue(models.Model):
    created = models.DateTimeField(auto_now_add=True)
    revision = models.IntegerField(default = 1)
    issue_date = models.DateTimeField(auto_now_add=True)
    issue_image_url = models.CharField(max_length=100)

class Page(models.Model):
    created = models.DateTimeField(auto_now_add=True)
    page_number = models.IntegerField()
    standard_page_url = models.CharField(max_length=100, default='')
    large_page_url = models.CharField(max_length=100, default='')
    thumbnail_url = models.CharField(max_length=100, default='')

    issue = models.ForeignKey(Issue, related_name="pages")

    class Meta:
        ordering = ('page_number',)

restAPI/serializers.py:

from rest_framework import serializers
from restAPI.models import Page, Issue

class IssueSerializer(serializers.ModelSerializer):
    class Meta:
        model = Issue
        fields = ('id', 'created', 'revision', 'issue_date', 'issue_image_url')

class PageSerializer(serializers.ModelSerializer):       
    class Meta:
        model = Page
        fields = ('id', 'created', 'page_number', 'standard_page_url', 'large_page_url', 'thumbnail_url')

restAPI/views.py:

from restAPI.models import Page, Issue
from restAPI.serializers import PageSerializer, IssueSerializer
from rest_framework import mixins
from rest_framework import generics

class IssueList(mixins.ListModelMixin,
                  mixins.CreateModelMixin,
                  generics.GenericAPIView):
    queryset = Issue.objects.all()
    serializer_class = IssueSerializer

    def get(self, request, *args, **kwargs):
        return self.list(request, *args, **kwargs)

    def post(self, request, *args, **kwargs):
        return self.create(request, *args, **kwargs)

class IssueDetail(mixins.RetrieveModelMixin,
                    mixins.UpdateModelMixin,
                    mixins.DestroyModelMixin,
                    generics.GenericAPIView):
    queryset = Issue.objects.all()
    serializer_class = IssueSerializer

    def get(self, request, *args, **kwargs):
        return self.retrieve(request, *args, **kwargs)

    def put(self, request, *args, **kwargs):
        return self.update(request, *args, **kwargs)

    def delete(self, request, *args, **kwargs):
        return self.destroy(request, *args, **kwargs)  

class PageList(mixins.ListModelMixin,
                  mixins.CreateModelMixin,
                  generics.GenericAPIView):
    queryset = Page.objects.all()
    serializer_class = PageSerializer

    def get(self, request, *args, **kwargs):
        print kwargs
        return self.list(request, *args, **kwargs)

    def post(self, request, *args, **kwargs):
        return self.create(request, *args, **kwargs)

class PageDetail(mixins.RetrieveModelMixin,
                   mixins.UpdateModelMixin,
                   mixins.DestroyModelMixin,
                   generics.GenericAPIView):
    queryset = Page.objects.all()
    serializer_class = PageSerializer

    def get(self, request, *args, **kwargs):
        return self.retrieve(request, *args, **kwargs)

    def put(self, request, *args, **kwargs):
        return self.update(request, *args, **kwargs)

    def delete(self, request, *args, **kwargs):
        return self.destroy(request, *args, **kwargs)

如何在issuespages之间实现这种关系

EN

回答 3

Stack Overflow用户

回答已采纳

发布于 2013-07-20 23:40:00

下面是我完成此操作的另一种方法:

views.py

from models import Customer, Order
from serializers import CustomerSerializer, OrderSerializer

from rest_framework import generics

class CustomerList(generics.ListCreateAPIView):
    queryset = Customer.objects.all()
    serializer_class = CustomerSerializer

class CustomerDetail(generics.RetrieveUpdateDestroyAPIView)
    queryset = Customer.objects.all()
    serializer_class = CustomerSerializer

class OrdersByCustomer(generics.ListCreateAPIView):
    queryset = Order.objects.all()
    serializer_class = OrderSerializer

    def get_queryset(self):
        customer_pk = self.kwargs['customer_pk']
        return self.queryset.filter(customer__pk=customer_pk)

    def pre_save(self, obj):
        obj.customer_id = self.kwargs['customer_pk'] 

class OrderDetail(generics.RetrieveUpdateDestroyAPIView):
    queryset = Order.objects.all()
    serializer_class = OrderSerializer

serializers.py

from models import Customer, Order

from rest_framework import serializers
from rest_framework.reverse import reverse

class OrderSerializer(serializers.HyperlinkedModelSerializer)

    class Meta:
        model = Order

class CustomerSerializer(serializers.HyperlinkedModelSerializer)

    orders = serializers.SerializerMethodField('get_customer_orders')

    def get_customer_orders(self, obj):
        return reverse('ordersbycustomer-list', 
               args=[obj.pk], request=self.context['request'])

    class Meta:
        model = Customer

urls.py

from django.conf.urls import patterns, include, url
from views import OrdersByCustomer, CustomerDetail, CustomerList

urlpatterns = patterns("",
    url(r'^customers/(?P<customer_pk>.+)/orders/$', OrdersByCustomer.as_view(), name='ordersbycustomer-list'),
    url(r'^customers/(?P<pk>.+)/$', CustomerDetail.as_view(), name='customer-detail'),
    url(r'^customers/$', CustomerList.as_view(), name='customer-list'),
    )

与视图集/路由器相比,涉及的代码更多,但这使您可以更好地控制正在发生的事情。

在这里,我选择仅将订单公开为客户的子项。由于它们是分开的,您可以使用不同的序列化程序类来处理list和detail。

票数 12
EN

Stack Overflow用户

发布于 2013-07-04 00:24:06

以下是我是如何使用Rest-Framework2.3版中的新ViewSetsRouters实现这一点的:

views.py:

from rest_framework import viewsets
from rest_framework.response import Response
from models import Order, OrderLine
from serializers import OrderSerializer, OrderLineSerializer

class OrderViewSet(viewsets.ModelViewSet):
    queryset = Order.objects.all()
    serializer_class = OrderSerializer

    @link()
    def lines(self, request, pk=None):
        queryset = OrderLine.objects.filter(order__pk=pk)
        serializer = OrderLineSerializer(queryset,
                           context={'request':request},
                           many=True)
        return Response(serializer.data)

class OrderLineViewSet(viewsets.ModelViewSet):
    queryset = OrderLine.objects.all()
    serializer_class = OrderLineSerializer

serializers.py

from rest_framework import serializers
from models import Order, OrderLine

class OrderSerializer(serializers.HyperlinkedModelSerializer):
    lines = serializers.HyperlinkedIdentityField(view_name='order-lines')

    class Meta:
        model = Order


class OrderLineSerializer(serializers.HyperlinkedModelSerializer):

    class Meta:
        model = OrderLine

urls.py

from views import OrderViewSet, OrderLineViewSet
from rest_framework.routers import DefaultRouter

router = DefaultRouter()
router.register(r'order', OrderViewSet)
router.register(r'orderline', OrderLineViewSet)
urlpatterns = router.urls

现在,' Order / id / Lines‘将返回一个序列化订单行的列表,这些订单行与由该id标识的订单具有关系。

当您向路由器注册视图时,用@link或@action修饰的ViewSet上的任何方法都将获得一个URL。

票数 8
EN

Stack Overflow用户

发布于 2014-07-17 19:15:42

我添加了def get_queryset(self):issue_id = self.kwargs'issue_id‘return Page.objects.filter(issue_id = issue_id)到PageList,现在GET works for issue/ /pages。现在我只需要弄清楚怎么发帖就行了。

我在PageList中添加了def pre_save(self,obj):obj.issue_id =self.kwargs‘’issue_id‘,现在POST也可以工作了。从一个不存在的问题中查询页面会返回一个空结果,而不是404 not found。如果有人知道做这件事的更好方法,我很想听听。

如果你的方法get_queryset(self)返回一个空列表而不是404Not FOUND,我建议使用django中的快捷函数get_list_or_404。该方法可能如下所示:

from django.shortcuts import get_list_or_404

def get_queryset(self):
    filter = {}
    filter['issue_id'] = self.kwargs['issue_id']
    return get_list_or_404(self.queryset, **filter)

我知道这是一个古老的帖子,但也许这可以帮助其他有相同或类似问题的人。

票数 1
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/17337843

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档