diff options
| author | Tom Christie | 2015-01-05 16:31:52 +0000 |
|---|---|---|
| committer | Tom Christie | 2015-01-05 16:31:52 +0000 |
| commit | d3b2302588f333b22d5e4aa2be6eca0e944e9494 (patch) | |
| tree | 7637f68a47870f02658fefcfba815f6d4ca80caf /docs/topics | |
| parent | 26ac2656e5e0b3d01a67551910113a305d2a2820 (diff) | |
| download | django-rest-framework-d3b2302588f333b22d5e4aa2be6eca0e944e9494.tar.bz2 | |
Minor docs update. Refs #2375.
Diffstat (limited to 'docs/topics')
| -rw-r--r-- | docs/topics/3.0-announcement.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/topics/3.0-announcement.md b/docs/topics/3.0-announcement.md index 68d24782..5dbc5600 100644 --- a/docs/topics/3.0-announcement.md +++ b/docs/topics/3.0-announcement.md @@ -87,12 +87,12 @@ The resulting API changes are further detailed below. #### The `.create()` and `.update()` methods. -The `.restore_object()` method is now replaced with two separate methods, `.create()` and `.update()`. - -These methods also replace the optional `.save_object()` method, which no longer exists. +The `.restore_object()` method is now removed, and we instead have two separate methods, `.create()` and `.update()`. These methods work slightly different to the previous `.restore_object()`. When using the `.create()` and `.update()` methods you should both create *and save* the object instance. This is in contrast to the previous `.restore_object()` behavior that would instantiate the object but not save it. +These methods also replace the optional `.save_object()` method, which no longer exists. + The following example from the tutorial previously used `restore_object()` to handle both creating and updating object instances. def restore_object(self, attrs, instance=None): |
