Django设置blank=True,null=True后仍触发外键约束完整性错误

Let's break down why you're hitting this error and walk through how to fix it step by step:

1. The Most Likely Culprit: Unapplied Migrations for the Driver Field #

You added blank=True, null=True to the driver field in your Order model, but if you didn't run Django migrations to apply this change to your database, the underlying database column is still set to NOT NULL. That's one of the most common gotchas in Django!

To resolve this:

• First, generate a migration file for the model change:

  python manage.py makemigrations
  

• Then apply the migration to update your database schema:

  python manage.py migrate
  

Double-check that the migration runs without errors—this will update the driver_id column in your Order table to allow NULL values, matching your model definition.

2. Validate the Restaurant ID is Valid #

When creating the Order, you're passing restaurant_id = request.POST["restaurant_id"] directly. If the ID you're sending in Postman doesn't correspond to an existing Restaurant instance, this will throw a foreign key constraint error too.

Add a validation check before creating the order to catch this early:

# Add this right before your order creation logic
try:
    restaurant = Restaurant.objects.get(id=request.POST["restaurant_id"])
except Restaurant.DoesNotExist:
    return JsonResponse({"status": "fail", "error": "Invalid restaurant ID provided"})

# Then use the restaurant instance instead of passing restaurant_id
order = Order.objects.create(
    customer=customer,
    restaurant=restaurant,  # Updated from restaurant_id=...
    total=order_total,
    status=Order.PENDING,
    address=request.POST["address"]
)

This not only prevents the constraint error but also gives you a clear, actionable error message for debugging.

3. Ensure the Customer Relationship Exists #

While less likely to be the immediate cause, confirm that access_token.user.customer actually points to an existing Customer instance. If the user doesn't have a related Customer object, accessing access_token.user.customer will throw a DoesNotExist exception—and if uncaught, this could manifest as an integrity error when saving the order.

4. Double-Check OrderDetails Meal IDs #

For completeness, when creating OrderDetails, make sure each meal["meal_id"] corresponds to a real Meal entry. You're already fetching the meal to calculate the subtotal, so wrapping that in a try/except can catch invalid IDs before they cause a constraint error:

for meal in order_details:
    try:
        meal_obj = Meal.objects.get(id=meal["meal_id"])
    except Meal.DoesNotExist:
        return JsonResponse({"status": "fail", "error": f"Meal with ID {meal['meal_id']} does not exist"})
    OrderDetails.objects.create(
        order=order,
        meal=meal_obj,  # Use the instance instead of meal_id
        quantity=meal["quantity"],
        sub_total=meal_obj.price * meal["quantity"]
    )

Quick Test After Fixes #

After applying the migrations and adding the validation checks, send your request again in Postman. If the error persists, check your database logs—they'll tell you exactly which foreign key constraint is failing (e.g., driver_id, restaurant_id, or customer_id), which narrows down the issue even more.

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