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.
This small change provides postgres support for ILIKE alongside LIKE. The "contains", "startsWith" and "endsWith" contraints only support "LIKE" And while it appears that the direct use of "LIKE" is supported (although undocumented) there is no equivalent pass-thru support for ILIKE.
I'd like to see this support flow over to mySQL, but that would have to come in the form of
COLLATE UTF8_GENERAL_CI like '%$search%'
Or something similar.
Also need to figure out why this affects populating associations.
A query with an association using like might end up as
"where": { "members.name": { "like": "%greenstreet%" } },
where as a query with an association using ilike will end up like
"where": { "members.name": { "members.ilike": "%greenstreet%" } },
I have yet to track down where this happens. Somehow the query building is smart enough to detect the presence of "like" but not "ilike"