-
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
Tagged with, wildcard #587
Comments
Congratulations, you found an Easter egg in the gem. It's a bug, i will fix it. |
Unfortunately, not this time
|
hmm TaggableModel.tagged_with(['bob'], wild: true).to_sql
"SELECT \"taggable_models\".* FROM \"taggable_models\" JOIN taggings taggable_mod_taggings_5ce8fb5 ON taggable_mod_taggings_5ce8fb5.taggable_id = taggable_models.id AND taggable_mod_taggings_5ce8fb5.taggable_type = 'TaggableModel' AND taggable_mod_taggings_5ce8fb5.tag_id = 1" Do you have a default scope ? |
Only on
|
add 'any: true' |
Thanks, that workaround works |
better to state this on the readme. Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have an issue with using tagged_with with wildcard. Calling it with a full name of a tag works great, but with only a part it does not. I decided to inspect it.
As I mentioned this one is ok, but calling it with only a part of a name should return at least one record but it does not.
Inspecting it deeper
Is there any logical explanation for
AND (1 = 0)
at the end of query?My environment:
rails (4.1.4)
acts-as-taggable-on (3.3.0), from ruby-gems
ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-darwin13.0]
The text was updated successfully, but these errors were encountered: