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

CRM-20740 - Fix issue with check for custom_nn => ['IS NULL' => 1]. #10512

Merged
merged 4 commits into from
Jun 16, 2017

Conversation

johanv
Copy link
Contributor

@johanv johanv commented Jun 15, 2017

This is a quick fix for CRM-20740. Using the API to retrieve entities with a custom field that IS NULL, now also works when there are entities without custom values in the custom field set.

A test would be nice. If I find the time, I will create one.


Johan Vervloet added 3 commits June 15, 2017 22:02
But since I have no working dev environment for the moment, I cannot
run it myself. I will push it, and see if it passes.

(If someone can check whether the tests fails on master, that would
be very nice.)
@seamuslee001
Copy link
Contributor

@johanv is there any reason why using a LEFT OUTER join rather than just a straight LEFT JOIN for when testing for NULL?

@johanv
Copy link
Contributor Author

johanv commented Jun 16, 2017

No. I thought that LEFT JOIN and LEFT OUTER JOIN were equivalent.

@seamuslee001
Copy link
Contributor

just did a quick google and your right no worries mate @johanv

@colemanw colemanw merged commit f74529d into civicrm:master Jun 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants