Is present and Is blank filter

[kweejibow]

Apologies in advance I'm quite new to rails and rails_admin.

Seem like the 'Is Present' and 'Is blank' column filters fail for any boolean value

It also fails when checking against the integer value of a FK object.

To better explain: I have a relationship between Client and Appointment, in my appointment list I include the field :client <-- where some automagick seems to display the clients name and create a link to that object. I can use all the other filters on the :client field just fine but if i try and check on Is Present or Is Blank the sql generated seems to try and check if client_id is not null and client_id != '' <-- which I believe is the issue.

Thanks!

[mshibuya]

Merging this into #1114.

[nroose]

Part of this issue is related to 1114, but not the boolean part. The fact is that the filter on boolean columns includes the is present and is blank entries on the list, but they cause a postgres error.

[mshibuya]

I know it, of course :)
My intention is that these tasks can be combined in that both of two require capability to build database column type sensitive SQL query in RailsAdmin ActiveRecord adapter.

[nicolasfranck]

The issue still exists in rails_admin/adapters/active_record.rb:

def unary_operators
          {
            '_blank' => ["(#{@column} IS NULL OR #{@column} = '')"],
            '_present' => ["(#{@column} IS NOT NULL AND #{@column} != '')"],
            '_null' => ["(#{@column} IS NULL)"],
            '_not_null' => ["(#{@column} IS NOT NULL)"],
            '_empty' => ["(#{@column} = '')"],
            '_not_empty' => ["(#{@column} != '')"]
          }
end

The line with '_present' leads to the postgres error:

ERROR:  invalid input syntax for type boolean

Reason: a column of type boolean is compared with an empty string.

[eminnett]

I can also replicate this issue. I may end up removing the options with JS which is a pretty dirty and unfortunate hack.

[nlsrchtr]

This is still relevant in 0.6.7. Is there some work going into the Postgres specifics?

[coorasse]

This error still exists. please reopen the issue.

[jhilden]

also still having the issue with 0.6.8

[hasan-aa]

No fix yet? Same issue exists with 0.8.1