Updated documentation for model indexing #2500
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Can you please add in a bit about what the index does and also add a notice header that it currently is only supported on Mongo and not MySQL/Postgres |
I have added a link to Mongodb's documentation on single field indexes, as there are several types of indexes. I did not add a comment about only working with Mongodb as the header of that section includes: Do you want me to add the comment about only working for mongodb anyway? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My PR is a:
Main update on the:
When working on a larger collection in mongo, I realized strapi did not add an index to a field I was querying against.
Upon tinkering with Strapi I found that adding index: true to a field configuration added the index automatically, but was not documented.