sharedinclude

Author: norareidy

source/crud/transactions.txt

@@ -53,61 +53,32 @@ instantiating a new client each time.
 Causal Consistency
 ~~~~~~~~~~~~~~~~~~
 
-MongoDB enables **causal consistency** in client sessions.
-The causal consistency model guarantees that operations within a session
-run in a causal order. Clients observe results that are consistent
-with the causal relationships, or the dependencies between
-operations. For example, if you perform a series of operations where
-one operation logically depends on the result of another, any subsequent
-reads reflect the dependent relationship.
+.. sharedinclude:: dbx/causal-consistency.rst
 
-The following table describes the guarantees that causally
-consistent sessions provide:
+   .. replacement:: insert-one-method
 
-.. list-table::
-   :widths: 40 60
-   :header-rows: 1
-
-   * - Guarantee
-     - Description
-
-   * - Read your writes
-     - Read operations reflect the results of preceding write operations.
-
-   * - Monotonic reads
-     - Read operations do not return results that reflect an earlier data state than
-       a preceding read operation.
+      ``insertOne()``
 
-   * - Monotonic writes
-     - If a write operation must precede other write operations, the driver
-       runs this write operation first.
+   .. replacement:: update-one-method
 
-       For example, if you call ``insertOne()`` to insert a document, then call
-       ``updateOne()`` to modify the inserted document, the driver runs the 
-       insert operation first.
+      ``updateOne()``
 
-   * - Writes follow reads
-     - If a write operation must follow other read operations, the driver runs
-       the read operations first.
+   .. replacement:: find-one-method
 
-       For example, if you call ``find()`` to retrieve a document, then call
-       ``deleteOne()`` to delete the retrieved document, the driver runs the find
-       operation first.
+      ``find()``
 
-In a causally consistent session, MongoDB ensures a
-causal relationship between the following operations:
+   .. replacement:: delete-one-method
 
-- Read operations that have a ``MAJORITY`` read concern
-- Write operations that have a ``MAJORITY`` write concern
+      ``deleteOne()``
 
-.. tip::
+   .. replacement:: majority-rc
 
-   To learn more about the concepts mentioned in this section, see the 
-   following {+mdb-server+} manual entries:
+      ``MAJORITY``
 
-   - :manual:`Causal Consistency </core/read-isolation-consistency-recency/#causal-consistency>`
-   - :manual:`Causal Consistency and Read and Write Concerns </core/causal-consistency-read-write-concerns/>`
+   .. replacement:: majority-wc
 
+      ``MAJORITY``
+      
 Methods
 -------