[DOCS-1340] Update#save docs should show the corresponding update being done. Created: 04/Apr/13 Updated: 03/Nov/17 Resolved: 05/Apr/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: http://docs.mongodb.org/manual/applications/update/ |
||
| Participants: | |
| Days since reply: | 10 years, 45 weeks, 5 days ago |
| Description |
|
http://docs.mongodb.org/manual/applications/update/#save If there is an _id value, then it should show the update statement used (including the upsert flag). A logical code block like this is probably the easiest way for most to understand when skimming.
|
| Comments |
| Comment by auto [ 05/Apr/13 ] |
|
Author: {u'date': u'2013-04-05T19:51:58Z', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by auto [ 05/Apr/13 ] |
|
Author: {u'date': u'2013-04-05T19:51:58Z', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |