Skip to content

Update data-model-operations.txt #1558

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Update data-model-operations.txt #1558

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions source/core/data-model-operations.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ These updates include pushing elements to an array (i.e.
:update:`$push`) and adding new fields to a document. If the document
size exceeds the allocated space for that document, MongoDB will
relocate the document on disk. Relocating documents takes longer than
*in place updates* updates and can lead to fragmented storage. Although
*in place updates* and can lead to fragmented storage. Although
MongoDB automatically :doc:`adds padding to document allocations
</core/record-padding>` to minimize the likelihood of relocation, data
models should avoid document growth when possible.
Expand All @@ -39,7 +39,7 @@ denormalized data model.

MongoDB adaptively adjusts the amount of automatic padding to reduce
occurrences of relocation. You may also use a *pre-allocation*
strategy to explicitly avoid document growth. Refer to
strategy to explicitly avoid document growth. Refer to the
:ecosystem:`Pre-Aggregated Reports Use Case
</use-cases/pre-aggregated-reports>` for an example of the
*pre-allocation* approach to handling document growth.
Expand All @@ -50,9 +50,9 @@ strategy to explicitly avoid document growth. Refer to
Atomicity
---------

In MongoDB, operations are atomic at the :term:`document` level: no
**single** write operation can change more than one document or more
than one collection. [#record-atomicity]_ Ensure that your application
In MongoDB, operations are atomic at the :term:`document` level. No
**single** write operation can change more than one document. Operations that modify more than a single document in a collection still operate on one document at a time.
[#record-atomicity]_ Ensure that your application
stores all fields with atomic dependency requirements in the same
document. If the application can tolerate non-atomic updates for two
pieces of data, you can store these data in separate documents.
Expand Down