Fix query builder bug when params[:q] specified #868
Merged
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.
Background
While developing a rails app with camaleon_cms I encountered a bug: #866
I guess it occurs only with postgresql, because I wrote a tmp test inside camaleon_cms gem(which uses sqllite in dummy app) and it wasn't failing.
The problem
The problem was wrong place of closing parenthesis of postgres function LOWER.
When it was after "?" sign, it was causing exception in PG query runner.
It was the query before fix:
The fix:
Move closing parenthesis of PG LOWER func to the of slug column.
More description details about the issue you can find here: #866