Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3601006
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 18, 20262026-05-18T20:34:01+00:00 2026-05-18T20:34:01+00:00

I am using Devise for authentication, so I’ve aliased a few columns in my

  • 0

I am using Devise for authentication, so I’ve aliased a few columns in my legacy database to accommodate it as follows:

class User < ActiveRecord::Base

  set_table_name 'my_legacy_user_table'
  set_primary_key 'UserId'
  alias_attribute :id, :UserId
  alias_attribute :username, :LoginId
  alias_attribute :encrypted_password, :PasswordSHA1Hash
  alias_attribute :first_name, :Name
  alias_attribute :last_name, :Surname

  devise :database_authenticatable, :authentication_keys => [:username]

  attr_accessible :username, :password, :password_confirmation

  def password_salt=(password_salt)
  end

  def password_salt
  end

  def password_digest(password)
    self.class.encryptor_class.digest(password)
  end

end

When I post to my /users/sign_in form, I get the following exception:

Mysql2::Error: Unknown column 'my_legacy_user_table.username' in 'where clause': SELECT `kms_User`.* FROM `my_legacy_user_table` WHERE (`my_legacy_user_table`.`username` = 'mrichman') LIMIT 1

I suppose I was under the assumption that alias_attribute would instruct ActiveRecord to use the real column name (UserId) and not the alias (username). What am I doing wrong?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-18T20:34:02+00:00Added an answer on May 18, 2026 at 8:34 pm

    Arel (the one that makes the SQL queries) still is not aware of ActiveRecord’s aliases (up to 3.0.3). You should make sure that the query is made using the original name, LoginId, in this case.

    If you enter the console and make a User.where(:username => “root”) you see that it generates an error, although User.username works well.

    For now just replace the username occurrences on sinup form until the upstream starts to support it.

    EDIT: By the way, the recommended way of doing that is make a view! Don’t forget that!
    http://www.slideshare.net/napcs/rails-and-legacy-databases-railsconf-2009

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am using Devise for authentication, so I've aliased a few columns in my
I am using devise but the User model is related to a legacy table
I'm using Devise for user authentication and basic authentication. Let's say I have defined
UPDATED I'm using Devise 1.4.9 for authentication and my Devise-generated User model doesn't seem
I'm Using Devise in my Rails 3.0.9 application for User Authentication. As I wanted
I'm using Devise for authentication, but I'm using two user models, Buyer and Seller.
I am using the devise gem for authentication and have the following before_filter in
I have already created a User Model using devise, but I now want to
I'm using Devise for authentication in my Rails app. I'd like to eager load
I have a rails app that is using Devise, with a User model, no

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.