If you're trying to bend the login engine plugin into a schema that
really doesn't match its assumptions, you're probably better copying
the code into your application properly, and then just adjusting it
and it's migrations directly - this kind of hacking (while certainly
possible) is just going to make things more complicated in the long
FYI, ActiveRecord has an 'alias_attribute' method which does exactly
what you're looking for, i.e.
class MyModel < ActiveRecord::Base
alias_attribute :your_name, :the_actual_column_name
This might only be in Edge Rails though; Caveat Coder.