@@ -725,22 +725,21 @@ content: |
725725 ---
726726ref : 4.2-changes-drivers-retryWrites-default
727727content : |
728- MongoDB 3.6 introduced support for :ref:`retryable-writes`, but most
729- official MongoDB 3.6 and 4.0-compatible drivers disabled this feature
730- by default. For such drivers, retryable writes could be enabled per
731- connection by including the :urioption:`retryWrites=true
732- <retryWrites>` option in the :ref:`connection string <mongodb-uri>`
733- for that connection. Refer to the `MongoDB Driver Documentation
734- <https://docs.mongodb.com/drivers/?tck=docs_server>`_ to determine
735- the correct default state of :urioption:`retryWrites` for your
736- specific driver and version.
737-
738- The official MongoDB 4.2+ compatible drivers enable :ref:`retryable-writes` by
739- default. Applications upgrading to the 4.2+ compatible drivers that require
740- retryable writes may omit the :urioption:`retryWrites=true <retryWrites>`
741- option. Applications upgrading to the 4.2+ compatible drivers that require
742- *disabling* retryable writes must include
743- :urioption:`retryWrites=false <retryWrites>` in the connection string.
728+
729+ Drivers compatible with MongoDB 4.2 and higher enable
730+ :ref:`retryable-writes` by default. Earlier drivers require the
731+ :urioption:`retryWrites=true <retryWrites>` option. The
732+ :urioption:`retryWrites=true <retryWrites>` option can be omitted in
733+ applications that use drivers compatible with MongoDB 4.2 and
734+ higher.
735+
736+ |
737+
738+ To disable retryable writes, applications that use drivers
739+ compatible with MongoDB 4.2 and higher must include
740+ :urioption:`retryWrites=false <retryWrites>` in the connection
741+ string.
742+
744743 ---
745744ref : 4.2-changes-libldap
746745content : |
0 commit comments