Skip to content

Commit 3b5d5ce

Browse files
committed
edit
1 parent 6c9b182 commit 3b5d5ce

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

source/crud/transactions.txt

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,10 @@ transaction is committed. If any operation in the transaction returns an
2727
error, the driver cancels the transaction and discards all data changes
2828
before they ever become visible.
2929

30+
In MongoDB, transactions run within logical **sessions**. A
31+
session is a grouping of related read or write operations that you
32+
intend to run sequentially.
33+
3034
When using the {+driver-short+}, you can create a new session from a
3135
``MongoClient`` instance as a ``ClientSession`` type. We recommend that you reuse
3236
your client for multiple sessions and transactions instead of
@@ -47,10 +51,6 @@ instantiating a new client each time.
4751
Causal Consistency
4852
~~~~~~~~~~~~~~~~~~
4953

50-
In MongoDB, transactions run within logical **sessions**. A
51-
session is a grouping of related read or write operations that you
52-
intend to run sequentially.
53-
5454
MongoDB enables **causal consistency** in client sessions, which allows
5555
you to execute operations in an :website:`ACID transaction </basics/acid-transactions>`.
5656
The causal consistency model guarantees that operations within a session
@@ -71,8 +71,8 @@ causal relationship between the following operations:
7171
To learn more about the concepts mentioned in this section, see the
7272
following {+mdb-server+} manual entries:
7373

74-
- :manual:`Server Sessions </reference/server-sessions/>`
7574
- :manual:`Causal Consistency </core/read-isolation-consistency-recency/#causal-consistency>`
75+
- :manual:`Causal Consistency and Read and Write Concerns </core/causal-consistency-read-write-concerns/>`
7676

7777
Methods
7878
-------

0 commit comments

Comments
 (0)