[server] Fixed issue with the adapters cache of a cloned EditedEntity The adapters' cache of the entity within an EditedEntity used to be copied along the entity itself during a cloning operation of the EditedEntity. This raises an issue when the adapters' cache is not empty and contains cached values linking to transaction-specific data (or the transaction itself). This prevents the clone EditedEntity being used in a transaction outside the one that created it. This change resets the adapters' cache of the new copy so that no cached value remain. The new copy can then be used in a new transaction afterwards.

     1

===================

     2

 Changelog history

     3

===================

     4

     5

.. include:: 3.26.rst

     6

.. include:: 3.25.rst

     7

.. include:: 3.24.rst

     8

.. include:: 3.23.rst

     9

.. include:: 3.22.rst

    10

.. include:: 3.21.rst

    11

.. include:: 3.20.rst

    12

.. include:: 3.19.rst

    13

.. include:: 3.18.rst

    14

.. include:: 3.17.rst

    15

.. include:: 3.16.rst

    16

.. include:: 3.15.rst

    17

.. include:: 3.14.rst