Skip to content

docs(dev): Mention new uniqueness check for index names #11550

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
susnux merged 2 commits into from
Mar 7, 2024
Merged

docs(dev): Mention new uniqueness check for index names #11550

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
04de7b5
docs(dev): Mention new uniqueness check for index names
joshtrichards Feb 17, 2024
11e7260
Update developer_manual/basics/storage/database.rst
joshtrichards Feb 28, 2024
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
Prev Previous commit
Update developer_manual/basics/storage/database.rst 
Co-authored-by: Joas Schilling <[email protected]>
Signed-off-by: Josh <[email protected]>
  • Loading branch information
@joshtrichards @nickvergessen
joshtrichards and nickvergessen authored Feb 28, 2024
commit 11e7260e71fddca868d5c213f271629aa73ba8b1
2 changes: 1 addition & 1 deletion developer_manual/basics/storage/database.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -360,7 +360,7 @@ It makes sense to apply some general tips from the beginning, so you don't have
<?php
$table->setPrimaryKey(['id']);

4. Manually set the name of your indexes. It will help you to manipulate them if needed in the future. Note that the names of the index are "global" database wide in some database platforms so having generic names can create conflicts. We check (as of v28) for uniqueness across all tables at installation time and during updates. This happens *regardless of the in-use database platform* to maintain broad compatibility (and consistency).
4. Manually set the name of your indexes. It will help you to manipulate them if needed in the future. Note that the names of the index are "global" database wide in some database platforms so having generic names can create conflicts. Since Nextcloud 28 uniqueness across all tables is ensured at installation time and during updates. This happens *regardless of the in-use database platform* to maintain broad compatibility and consistency.

.. code-block:: php

Expand Down