Commit c1d3f340 authored by Jonathan Pasquier's avatar Jonathan Pasquier

Minor edit to fix formatting glitches

The first paragraph of section 6.1 has some minor formatting errors (see http://docs.doctrine-project.org/projects/doctrine-dbal/en/latest/reference/transactions.html#transaction-nesting)
Removing a couple of spaces fixes the problem.
parent de6c0bd2
...@@ -60,9 +60,9 @@ transactions, or rather propagating transaction control up the call ...@@ -60,9 +60,9 @@ transactions, or rather propagating transaction control up the call
stack. For that purpose, the ``Connection`` class keeps an internal stack. For that purpose, the ``Connection`` class keeps an internal
counter that represents the nesting level and is counter that represents the nesting level and is
increased/decreased as ``beginTransaction()``, ``commit()`` and increased/decreased as ``beginTransaction()``, ``commit()`` and
``rollBack()`` are invoked. ``beginTransaction()`` increases the ``rollBack()`` are invoked. ``beginTransaction()`` increases the
nesting level whilst nesting level whilst
``commit()`` and ``rollBack()`` decrease the nesting level. The nesting level starts at 0. Whenever the nesting level transitions from 0 to 1, ``beginTransaction()`` is invoked on the underlying driver connection and whenever the nesting level transitions from 1 to 0, ``commit()`` or ``rollBack()`` is invoked on the underlying driver, depending on whether the transition was caused by ``Connection#commit()`` or ``Connection#rollBack()``. ``commit()`` and ``rollBack()`` decrease the nesting level. The nesting level starts at 0. Whenever the nesting level transitions from 0 to 1, ``beginTransaction()`` is invoked on the underlying driver connection and whenever the nesting level transitions from 1 to 0, ``commit()`` or ``rollBack()`` is invoked on the underlying driver, depending on whether the transition was caused by ``Connection#commit()`` or ``Connection#rollBack()``.
What this means is that transaction control is basically passed to What this means is that transaction control is basically passed to
code higher up in the call stack and the inner transaction block is code higher up in the call stack and the inner transaction block is
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment