Django单个接口创建带关联关系的多个对象的实现方案

你需要的核心能力是数据库原子事务配合嵌套序列化器，完全不用手动编写回滚逻辑，方案如下：

推荐方案：嵌套序列化器+事务封装（符合DRF设计规范） #

把关联创建的逻辑全部封装到序列化器层，事务保证两个模型的创建操作要么全部成功，要么全部自动回滚，不会残留无效的Goal数据。

序列化器实现 #

from rest_framework import serializers
from django.db import transaction
from .models import Goal, Post

class GoalSerializer(serializers.ModelSerializer):
    class Meta:
        model = Goal
        fields = ["goal_category", "description"]

class PostWithGoalSerializer(serializers.ModelSerializer):
    # 嵌套接收Goal相关参数，write_only表示不需要返回给前端
    goal = GoalSerializer(write_only=True)
    
    class Meta:
        model = Post
        fields = ["body", "goal"]
    
    def create(self, validated_data):
        goal_data = validated_data.pop("goal")
        # 原子事务上下文：中间任意步骤报错，所有数据库操作自动回滚
        with transaction.atomic():
            # 从请求上下文取当前用户，不用前端传递，避免恶意伪造
            goal = Goal.objects.create(
                creator_uuid=self.context["request"].user,
                **goal_data
            )
            post = Post.objects.create(
                creator_uuid=self.context["request"].user,
                goal_uuid=goal,
                **validated_data
            )
        return post

视图层实现 #

from rest_framework.decorators import api_view
from rest_framework.response import Response
from .serializers import PostWithGoalSerializer

@api_view(["POST"])
def post(request):
    """
    当前用户创建带关联Goal的Post接口
    """
    # 传入request上下文给序列化器获取当前用户
    serializer = PostWithGoalSerializer(data=request.data, context={"request": request})
    # 校验失败自动返回400响应，无需手动判断
    serializer.is_valid(raise_exception=True)
    serializer.save()
    return Response(serializer.data, status=201)

轻量修改方案：原有逻辑加事务即可 #

如果你不想重构序列化器结构，只需要给原有视图逻辑加上原子事务包裹，即可省去手动删除Goal的代码：

from django.db import transaction
from rest_framework.decorators import api_view
from rest_framework.response import Response

@api_view(["POST"])
def post(request):
    """
    当前用户创建带关联Goal的Post接口
    """
    with transaction.atomic():
        goal_serializer = GoalSerializer(data=request.data)
        goal_serializer.is_valid(raise_exception=True)
        # 直接传入当前用户保存，不用前端传creator_uuid更安全
        goal_obj = goal_serializer.save(creator_uuid=request.user)
        
        # 注意你原有代码这里有笔误：uud改为uuid，且无需转字符串，直接传实例即可
        post_serializer = PostSerializer(data=request.data)
        post_serializer.is_valid(raise_exception=True)
        post_serializer.save(creator_uuid=request.user, goal_uuid=goal_obj)
    
    return Response(post_serializer.data, status=201)

方案优势 #

• 原子性保证：所有数据库操作要么全部成功，要么全部自动回滚，不会产生脏数据
• 逻辑分层清晰：关联创建逻辑封装在序列化器层，视图只处理请求响应，后续易维护
• 安全性更高：用户ID直接从登录态取，避免前端恶意传参伪造数据
• 代码更简洁：无需手动编写校验失败的返回逻辑、手动回滚删除逻辑

内容的提问来源于stack exchange，提问作者user12314098