Don't use LIKE query when we have the full uid #30155
Closed
Conversation
This file contains hidden or 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
Signed-off-by: Louis Chemineau <[email protected]>
artonge
force-pushed
the
perf/make_like_optional_in_contacts_search
branch
from
1e14ef1 to
1580863
Compare
Member
|
Took over the bits into #30156 |
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.
Rational
CloudIdManager::getDisplayNameFromContactspecifically checks for a strictly matchingcloudIdin the results, so a LIKE query is superfluous.This PR adds an option to use an equivalence query
=inCardDavBackend::searchByAddressBookIdsto improve matching speed.CloudIdManager::getDisplayNameFromContactnow uses this option.Follow up of #27884