github-migration/mongo-ruby-driver
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #98 from ismell/patch-1

Browse Source 
Fixed a typo
This commit is contained in:
gjmurakami-10gen 2012-05-14 13:57:07 -07:00
commit f5dc37fe68
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/WRITE_CONCERN.md
View File

@ -9,7 +9,7 @@ Write concern is set using the `:safe` option. There are several possible option
@collection.save({:doc => 'foo'}, :safe => {:w => 2, :wtimeout => 200}) @collection.save({:doc => 'foo'}, :safe => {:w => 2, :wtimeout => 200})
@collection.save({:doc => 'foo'}, :safe => {:w => 2, :wtimeout => 200, :j => true}) @collection.save({:doc => 'foo'}, :safe => {:w => 2, :wtimeout => 200, :j => true})
The first, `true`, simply indicates that we should request a response from the server to ensure that to errors have occurred. The second, `{:w => 2}`, forces the server to wait until at least two servers have recorded the write. The third does the same but will time out if the replication can't be completed in 200 milliseconds. The first, `true`, simply indicates that we should request a response from the server to ensure that no errors have occurred. The second, `{:w => 2}`, forces the server to wait until at least two servers have recorded the write. The third does the same but will time out if the replication can't be completed in 200 milliseconds.
Setting a value for `wtimeout` is encouraged. Setting a value for `wtimeout` is encouraged.
Finally, the fourth example forces the journal to sync to disk if journaling is enabled. Finally, the fourth example forces the journal to sync to disk if journaling is enabled.