-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Bad SQL creation from a filter #4078
Comments
Please check this on the Rails console: User.ransack(email_cont: "jas").result Which database query will be performed and is the result right? |
[1] pry(main)> User.ransack(email_cont: "jas").result User Load (1.0ms) SELECT "users".* FROM "users" WHERE "users"."deleted_at" IS NULL AND ("users"."email" ILIKE '%jas%') => [#<User:0x007f8f0aed14f8 |
and this: User.ransack(email_contains: "jas").result |
Ok
|
Does this mean it's actually a Ransack issue? |
Whats happen if you request this URL on your system?
|
Do you use any custom ransacker? |
Same, this is what first surfaced the error.
I have the following in our User model.
Nothing relating to |
Did you have seen the change that I have made in the url?
|
Sorry!
Works. Of course the URL we are using is generated by ActiveAdmin. |
You should can fix your problem with: filter :email, filters: [:cont, :eq, :start, :end] But you need to add some traslations |
@timoschilling shouldn't https://github.com/activeadmin/activeadmin/blob/master/lib/ransack_ext.rb be mapping Any clues why this isn't happening? |
Yes, but it seams to not work in your case. It's happen, otherwise you will get a non method error, but it don't work. |
This was caused by a bad ransack config that wasn't found before. |
When doing a filter on email (contains) I'm getting the following error (see below).
(please note: already updated the gem to git head, problem still occurs.)
Any help would be much appreciated.
excerpt from stacktrace:
users.email
from schema.db...Full stack trace
The text was updated successfully, but these errors were encountered: