From a266488eba48e96216ff379a1396ed2998036e88 Mon Sep 17 00:00:00 2001 From: maspwr Date: Sun, 17 Feb 2013 20:02:54 -0800 Subject: [PATCH] Updated Writable Nested Serializers (markdown) --- Writable-Nested-Serializers.md | 1 - 1 file changed, 1 deletion(-) diff --git a/Writable-Nested-Serializers.md b/Writable-Nested-Serializers.md index d847089..2298f7c 100644 --- a/Writable-Nested-Serializers.md +++ b/Writable-Nested-Serializers.md @@ -2,5 +2,4 @@ Ongoing discussion questions/answers for the writable nested serializers: * Should we let nested models be disassociated/orphaned (FK set to null) vs. outright deletion? Outright deletion seems like the more common use case. If I have an album with tracks, I probably want to delete the actual track model not just orphan it. -* Is the `_delete` keyword for deletion the best method? Setting a nested model field to `None` might be nicer in the one-to-one case, but doesn't translate well to one-to-many.