Skip to content

Commit aee5168

Browse files
authored
Merge pull request #12949 from nextcloud/backport/12864/stable30
[stable30] feat(devmanual): Clarify behavior of missing replacement indexes
2 parents 9a48bb1 + 0d2d56c commit aee5168

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

developer_manual/basics/storage/migrations.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -198,6 +198,8 @@ Replacing indices
198198

199199
Similar to adding an index to an existing table, it could be necessary to replace one or more indices with a new one. To avoid a gap between dropping the old indices in a migration and adding the new one through ``AddMissingIndicesEvent``, it is possible to do both at once in ``AddMissingIndicesEvent``.
200200

201+
If none of the previous indices are found, e.g. because they were optional and not created yet, the replacement index will be treated as *missing index*.
202+
201203
.. note:: Make sure to not use the same index name for the new index as for old indices.
202204

203205
.. code-block:: php

0 commit comments

Comments
 (0)