Skip to content

Fix typo: tnx -> txn #4063

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

Merged
merged 1 commit into from
Feb 26, 2024
Merged

Fix typo: tnx -> txn #4063

Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion doc/concepts/atomic/txn_mode_default.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Transaction mode: default
===========================

By default, Tarantool does not allow :ref:`"yielding" <app-yields>` inside a :ref:`memtx <engines-chapter>`
transaction and the :ref:`transaction manager <txn_mode_mvcc-tnx-manager>` is disabled. This allows fast
transaction and the :ref:`transaction manager <txn_mode_mvcc-txn-manager>` is disabled. This allows fast
atomic transactions without conflicts, but brings some limitations:

* You cannot use :ref:`interactive transactions <txn_mode_interactive_transaction>`.
Expand Down
4 changes: 2 additions & 2 deletions doc/concepts/atomic/txn_mode_mvcc.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ but has a different implementation.

Currently, you cannot use several different storage engines within one transaction.

.. _txn_mode_mvcc-tnx-manager:
.. _txn_mode_mvcc-txn-manager:

Transaction manager
-------------------
Expand Down Expand Up @@ -97,7 +97,7 @@ You can set an isolation level for a specific transaction in its ``box.begin()``

.. code-block:: lua

box.begin({ tnx_isolation = 'best-effort' })
box.begin({ txn_isolation = 'best-effort' })

In this case, you can also use the ``default`` option. It sets the transaction's isolation level
to the one set in ``box.cfg``.
Expand Down
4 changes: 2 additions & 2 deletions doc/concepts/data_model/indexes.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -260,7 +260,7 @@ RTREE index can accept two types of ``distance`` functions: ``euclid`` and ``man
.. warning::

Currently, the :ref:`isolation level <transaction_model_levels>` of RTREE indexes
in :ref:`MVCC transaction mode <txn_mode_mvcc-tnx-manager>` is *read-committed* (not *serializable*, as stated).
in :ref:`MVCC transaction mode <txn_mode_mvcc-txn-manager>` is *read-committed* (not *serializable*, as stated).
If a transaction uses these indexes, it can read committed or confirmed data (depending on the isolation level).
However, the indexes are subject to different anomalies that can make them unserializable.

Expand Down Expand Up @@ -443,7 +443,7 @@ attributes.
.. warning::

Currently, the :ref:`isolation level <transaction_model_levels>` of BITSET indexes
in :ref:`MVCC transaction mode <txn_mode_mvcc-tnx-manager>` is *read-committed* (not *serializable*, as stated).
in :ref:`MVCC transaction mode <txn_mode_mvcc-txn-manager>` is *read-committed* (not *serializable*, as stated).
If a transaction uses these indexes, it can read committed or confirmed data (depending on the isolation level).
However, the indexes are subject to different anomalies that can make them unserializable.

Expand Down