Dedupe performance - hard-remove financial_item from list of dymnamic refs to contact table #17567
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.
Overview
Rc fix for performance regression in deduping - note I want to see if we can do a better fix onn master
Before
SQL runs:
select id FROM civicrm_financial_item WHERE entity_table = 'civicrm_contact';
to see if the table is a dedupe candidate.However, the index on this table does not cover the where clause & as this is a large table it gets slow
After
Query hacked out of the list
Technical Details
For the 'real' fix on master I think we want a schema for this - ie something like
Note there is a previous pointer to this approach
civicrm-core/CRM/Core/DAO.php
Line 2407 in 449c4e6
Comments
@totten @seamuslee001 @colemanw a couple of questions