Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A administrate
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 96
    • Issues 96
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 32
    • Merge requests 32
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • thoughtbot, inc.
  • administrate
  • Issues
  • #178
Closed
Open
Issue created Nov 06, 2015 by Administrator@rootContributor

Devise inet fields may be treated as Field::String in Administrate, which results in SQL errors when searching

Created by: maxkwallace

I'm seeing an ActiveRecord::StatementInvalid error when searching over my Users in Administrate.

Postgres gives the following error:

PG::UndefinedFunction: ERROR:  function lower(inet) does not exist

The SQL query that's erroring looks like:

SELECT  "users".* FROM "users" WHERE (lower(email) LIKE '%george%' OR lower(current_sign_in_ip) LIKE '%george%' ... ) LIMIT 20 OFFSET 0

As far as I can tell, this is because the current_sign_in_ip attribute (managed by Devise) is treated as a String in Administrate:

    current_sign_in_ip: Field::String,

whereas it's actually an inet in Postgres:

t.inet     "current_sign_in_ip"

so attempting to use lower on it fails.

This isn't an urgent issue-- simply deleting the offending attributes from ATTRIBUTE_TYPES in my user_dashboard.rb file allows me to search just fine. The only downside is that I can't see the current_sign_in_ip attribute in Administrate, which really doesn't matter. But I thought it was worth reporting.

Assignee
Assign to
Time tracking