Update MongoDB Manual with Write Concern Change (DOCS-696)

[DOCS-704] Update Manual Tutorials and Use Cases with Write Cocern Page Created: 31/Oct/12  Updated: 19/Nov/12  Resolved: 19/Nov/12

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Sub-task Priority: Major - P3
Reporter: Sam Kleinman (Inactive) Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 11 years, 13 weeks, 2 days ago

 Description   

> - source/use-cases/inventory-management
> - source/use-cases/metadata-and-asset-management
> - source/use-cases/storing-log-data



 Comments   
Comment by auto [ 19/Nov/12 ]

Author:

{u'date': u'2012-11-19T22:28:53Z', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}

Message: DOCS-704 changes and updates for write concern change
Branch: master
https://github.com/mongodb/docs/commit/6b519ee8e5ad8117351fbb340c041b9b12c3f185

Comment by Sam Kleinman (Inactive) [ 15/Nov/12 ]

edited description to remove examples that were included because they use the word "safe" in another context.

The remaining documents just depend on the new write concern syntax of the python driver, for the update/insert method.

Not blocking for the release of the write concern change.

Generated at Thu Feb 08 07:39:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.