-
-
Notifications
You must be signed in to change notification settings - Fork 825
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.
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
dev/core#1725 Only export primary address fields #17458
Conversation
Per ticket the queries just don't work otherwise....
(Standard links)
|
@jitendrapurohit can you test this - it should help on at least the site I did testing on (which had searchPrimaryOnly disabled on 20 April) |
@eileenmcnaughton I think @jitendrapurohit already did as part of their report on #17444 "I tried to force the primary option by applying #17458 PR to the site. The query formed do have the condition of table.is_primary = 1 but it still takes too long to complete the process. Full Query -
This is while searching for contacts with activity type = x on advanced search and then export. |
@seamuslee001 yes - this solves an issue where the problem is not the groups & tags - the site I looked at had changed on Apr 20 & the group_contact_cache was not the issue on it Probably the group contact cache should not be joined in at all above since we should not include smart groups IMHO |
@seamuslee001 so my opinion is this is BETTER performance than without it - it just doesn't solve everything.... |
I've given this 'has-test' as I added extensive testing on this previously |
I tested this and whilst it does enforce the primary fields it doesn't affect someone selecting say an address location type that isn't the one that is primary and the data is still correctly returned. Merging |
Overview
Addresses server crashing on export when primary only is disabled
Before
Grown servers brought to their knees
After
Improved
Technical Details
Let's see how tests go since cover is good.
Comments