Skip to content

Commit ffa2f8f

Browse files
committed
Docsp 42960 nested components (#387)
* DOCSP-42960: Removing nested components in go pages * DOCSP-42960: Removing nested components in go pages * DOCSP-42960: Removing nested components spacing updates * DOCSP-42960: Removing nested components fixing rst error (cherry picked from commit cb6466d)
1 parent 1690a55 commit ffa2f8f

File tree

3 files changed

+15
-11
lines changed

3 files changed

+15
-11
lines changed

source/fundamentals/crud/read-operations/retrieve.txt

+2-5
Original file line numberDiff line numberDiff line change
@@ -111,11 +111,8 @@ following methods:
111111
* - ``SetLimit()``
112112
- | The maximum number of documents to return.
113113
| Default: ``0``
114-
115-
.. note::
116-
117-
This option is not available for ``FindOneOptions``. The
118-
``FindOne()`` method internally uses ``SetLimit(-1)``.
114+
| This option is not available for ``FindOneOptions``. The
115+
``FindOne()`` method internally uses ``SetLimit(-1)``.
119116

120117
* - ``SetProjection()``
121118
- | The fields to include in the returned documents.

source/fundamentals/run-command.txt

+2-6
Original file line numberDiff line numberDiff line change
@@ -90,12 +90,8 @@ with the following fields:
9090

9191
* - ``operationTime``
9292
- Indicates the logical time of the operation. MongoDB uses the
93-
logical time to order operations.
94-
95-
.. seealso::
96-
97-
To learn more about logical time, see our :website:`blog post about
98-
the Global Logical Clock </blog/post/transactions-background-part-4-the-global-logical-clock>`.
93+
logical time to order operations. To learn more about logical time, see our :website:`blog post about
94+
the Global Logical Clock </blog/post/transactions-background-part-4-the-global-logical-clock>`.
9995

10096
* - ``$clusterTime``
10197
- Provides a document that returns the signed cluster time. Cluster time is a

source/fundamentals/transactions.txt

+11
Original file line numberDiff line numberDiff line change
@@ -93,6 +93,7 @@ following table describes these methods:
9393
error if there is no active transaction for the session or if the
9494
transaction was ended. To learn more about
9595
this method, see the :manual:`commitTransaction() page
96+
<<<<<<< HEAD
9697
</reference/method/Session.commitTransaction/>` in the Server manual.
9798

9899
.. note:: Retrying a Transaction
@@ -105,6 +106,16 @@ following table describes these methods:
105106
``UnknownTransactionCommitResult`` label. If you rerun the
106107
``CommitTransaction()`` method after receiving this error,
107108
your data is not changed by the repeat attempts.
109+
=======
110+
</reference/method/Session.commitTransaction/>` in the Server manual.
111+
|
112+
| The ``CommitTransaction()`` method is an idempotent function, which
113+
means that you can attempt to commit a transaction multiple times without changing data after the first successful commit.
114+
A transaction can succeed but return an error with the
115+
``UnknownTransactionCommitResult`` label. If you rerun the
116+
``CommitTransaction()`` method after receiving this error,
117+
your data is not changed by the repeat attempts.
118+
>>>>>>> cb6466d (Docsp 42960 nested components (#387))
108119

109120
|
110121
| **Parameter**: ``Context``

0 commit comments

Comments
 (0)