mirror of
https://github.com/encode/django-rest-framework.git
synced 2025-03-03 19:00:17 +03:00
Changed formatting and updated docs
This commit is contained in:
parent
2946251c91
commit
dae5426e20
|
@ -747,6 +747,8 @@ To support multiple updates you'll need to do so explicitly. When writing your m
|
||||||
* How should insertions be handled? Are they invalid, or do they create new objects?
|
* How should insertions be handled? Are they invalid, or do they create new objects?
|
||||||
* How should removals be handled? Do they imply object deletion, or removing a relationship? Should they be silently ignored, or are they invalid?
|
* How should removals be handled? Do they imply object deletion, or removing a relationship? Should they be silently ignored, or are they invalid?
|
||||||
* How should ordering be handled? Does changing the position of two items imply any state change or is it ignored?
|
* How should ordering be handled? Does changing the position of two items imply any state change or is it ignored?
|
||||||
|
|
||||||
|
You will need to add an explicit `id` field to the instance serializer. The default implicitly-generated `id` field is marked as `read_only`. This causes it to be removed on updates. Once you declare it explicitly, it will be available in the list serializer's `update` method.
|
||||||
|
|
||||||
Here's an example of how you might choose to implement multiple updates:
|
Here's an example of how you might choose to implement multiple updates:
|
||||||
|
|
||||||
|
@ -774,10 +776,7 @@ Here's an example of how you might choose to implement multiple updates:
|
||||||
|
|
||||||
class BookSerializer(serializers.Serializer):
|
class BookSerializer(serializers.Serializer):
|
||||||
...
|
...
|
||||||
id = serializers.IntegerField(
|
id = serializers.IntegerField(required=False)
|
||||||
read_only=False,
|
|
||||||
required=False
|
|
||||||
)
|
|
||||||
|
|
||||||
class Meta:
|
class Meta:
|
||||||
list_serializer_class = BookListSerializer
|
list_serializer_class = BookListSerializer
|
||||||
|
|
Loading…
Reference in New Issue
Block a user