-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
strict_case_match doesn't work as expected #965
Comments
endorfin
added a commit
to endorfin/acts-as-taggable-on
that referenced
this issue
Sep 5, 2019
arel matches and matches_any has a third parameter for case sensitivity, that was not set and always false. So ActsAsTaggableOn.strict_case_match didn't work with PostgreSQL
pull request #966 |
Andythurlow
pushed a commit
to Andythurlow/acts-as-taggable-on
that referenced
this issue
Mar 5, 2020
arel matches and matches_any has a third parameter for case sensitivity, that was not set and always false. So ActsAsTaggableOn.strict_case_match didn't work with PostgreSQL
seuros
pushed a commit
that referenced
this issue
May 7, 2020
This one could be closed now I think as #966 merged |
Thanks! |
This was referenced Mar 12, 2021
rolandoalvarado
pushed a commit
to rolandoalvarado/acts-as-taggable-on
that referenced
this issue
Nov 11, 2021
arel matches and matches_any has a third parameter for case sensitivity, that was not set and always false. So ActsAsTaggableOn.strict_case_match didn't work with PostgreSQL Co-authored-by: René Kersten <rene.kersten@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As I noticed today, the option ActsAsTaggableOn.strict_case_match = true only works for creating new tags, but not with the tagged_with scope.
After a little research I found out that the third parameter case_sensitive for matches and matches_any in query_base.rb (tag_match_type, tags_match_type) isn't set.
So there is always a search with ILIKE.
The text was updated successfully, but these errors were encountered: