Skip to content
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

Prev next #13533

Merged
merged 3 commits into from
Feb 5, 2019
Merged

Prev next #13533

merged 3 commits into from
Feb 5, 2019

Conversation

eileenmcnaughton
Copy link
Contributor

Overview

Fix search regressions introduced in 5.9 relating to caching & custom searches

Before

Under some circumstances searches which output tags or groups present all contacts in a single row

After

Correct number of rows returned

Technical Details

This arises because 'GROUP_CONCAT' is used without the GROUP BY clause due to

eileenmcnaughton@2ca46d4#diff-e54381bfdf51e31cab376c71ca0d66ffR4967

There is some somewhat unrelated bugginess about the inclusion of groups & tags that makes this hard to replicate :-(

Comments

I have also pulled in #13531 which I think is a related regression & should also go into the rc

eileenmcnaughton and others added 2 commits February 5, 2019 12:59
The bug as described was a bit tricksy to replicate as it is inconsistent and the
code is not actually outputting the tags/ groups. I think these are pre-existing issues

I was able to replicate by having 2 search profiles - one with only tags & one one with only groups & switching back & and force on output -  once I replicated I found that there was a regression due to

2ca46d4#diff-e54381bfdf51e31cab376c71ca0d66ffR4967

whereby the groupBy had been dropped, causing the results to be squashed into a single row
@civibot
Copy link

civibot bot commented Feb 5, 2019

(Standard links)

@civibot civibot bot added the 5.10 label Feb 5, 2019
@seamuslee001
Copy link
Contributor

The change looks fine to me, i'm just going to go through a quick r-run now

@seamuslee001
Copy link
Contributor

I have done an r-run and can't see any issues with this PR. adding merge on pass

This prevents an error when using the cache and allows us to move
past this without untangling the messy way other tables are joined back in
for now.

Note it became necessary due to query changes off the cache but the query is no
different in accuracy
@eileenmcnaughton
Copy link
Contributor Author

We hit a full group by bug :-( - I've extended the cases where fgb is disabled to cope

@eileenmcnaughton eileenmcnaughton merged commit bcc1969 into civicrm:5.10 Feb 5, 2019
@eileenmcnaughton
Copy link
Contributor Author

unrelated fails

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants