25

我在运行测试时遇到了这个错误。我已经检查以确保所有的email_confirmations 拼写正确并且（除非我疯了）它们是正确的。我有点像 Rails 菜鸟，所以它可能很简单。

用户模型

class User < ActiveRecord::Base
  attr_accessible :email, :email_confirmation, :first_name, :last_name,
                  :password, :password_confirmation
  has_secure_password

  before_save { |user| user.email = email.downcase }

  validates :first_name, presence: true, length: { maximum: 25 }
  validates :last_name, presence: true, length: { maximum: 25 }
  VALID_EMAIL_REGEX = /\A[\w+\-.]+@[a-z\d\-.]+\.[a-z]+\z/i
  validates :email, presence: true, format: { with: VALID_EMAIL_REGEX },
                    uniqueness: { case_sensitive: false }
  validates :email_confirmation, presence: true
  validates :password, presence: true, length: { maximum: 6 }
  validates :password_confirmation, presence: true
end

Rspec 测试

require 'spec_helper'

describe User do
  before { @user = User.new(email: "user@example.com",
                            first_name: "John", last_name: "Smith",
                            password: "foobar", password_confirmation: "foobar",
                            email_confirmation: "user@example.com") }

  subject { @user }

  it { should respond_to(:first_name) }
  it { should respond_to(:last_name) }
  it { should respond_to(:email) }
  it { should respond_to(:email_confirmation) }
  it { should respond_to(:password_digest) }
  it { should respond_to(:password) }
  it { should respond_to(:password_confirmation) }
  it { should respond_to(:authenticate) }

  it { should be_valid }

  describe "when first name is not present" do
    before { @user.first_name = " " }
    it { should_not be_valid }
  end

  describe "when last name is not present" do
    before { @user.last_name = " " }
    it { should_not be_valid }
  end

  describe "when email is not present" do
    before { @user.email = @user.email_confirmation = " " }
    it { should_not be_valid }
  end

  describe "when password is not present" do
    before { @user.password = @user.password_confirmation = " " }
    it { should_not be_valid }
  end

  describe "when first_name is too long" do
    before { @user.first_name = "a" * 26 }
    it { should_not be_valid }
  end

  describe "when last_name is too long" do
    before { @user.last_name = "a" * 26 }
    it { should_not be_valid }
  end

  describe "when email format is invalid" do
    it "should be invalid" do
      addresses = %w[user@foo,com user_at_foo.org example.user@foo.
                             foo@bar_baz.com foo@bar+baz.com]
      addresses.each do |invalid_address|
        @user.email = invalid_address
        @user.should_not be_valid
     end      
    end
  end

  describe "when email format is valid" do
    it "should be valid" do
      addresses = %w[user@foo.COM A_US-ER@f.b.org frst.lst@foo.jp a+b@baz.cn]
      addresses.each do |valid_address|
        @user.email = valid_address
        @user.should be_valid
      end      
    end
  end

  describe "when email address is already taken" do
    before do
      user_with_same_email = @user.dup
      user_with_same_email.email = @user.email.upcase
      user_with_same_email.save
    end

    it { should_not be_valid }
  end

  describe "when password doesn't match confirmation" do
    before { @user.password_confirmation = "mismatch" }
    it { should_not be_valid }
  end

  describe "when email doesn't match confirmation" do
    before { @user.email_confirmation = "mismatch@example.com" }
    it { should_not be_valid }
  end

  describe "when password confirmation is nil" do
    before { @user.password_confirmation = nil }
    it { should_not be_valid }
  end

  describe "when email confirmation is nil" do
    before { @user.email_confirmation = nil }
    it { should_not be_valid }
  end

  describe "with a password that's too short" do
    before { @user.password = @user.password_confirmation = "a" * 5 }
    it { should be_invalid }
  end

  describe "return value of authenticate method" do
    before { @user.save }
    let(:found_user) { User.find_by_email(@user.email) }

    describe "with valid password" do
      it { should == found_user.authenticate(@user.password) }
    end

    describe "with invalid password" do
      let(:user_for_invalid_password) { found_user.authenticate("invalid") }

      it { should_not == user_for_invalid_password }
      specify { user_for_invalid_password.should be_false }
    end
  end
end

架构.rb

ActiveRecord::Schema.define(:version => 20130417021135) do

  create_table "users", :force => true do |t|
    t.string   "first_name"
    t.string   "last_name"
    t.string   "email"
    t.datetime "created_at",      :null => false
    t.datetime "updated_at",      :null => false
    t.string   "password_digest"
  end

  add_index "users", ["email"], :name => "index_users_on_email", :unique => true

end
4

6 回答 6

29

你得到UnknownAttributeError是因为你的users表中没有名为email_confirmation. 默认情况下，ActiveRecord 将查找与您用于构造模型的属性名称相同的 DB 列，但此行试图使用数据库不知道的属性构造用户：

  before { @user = User.new(email: "user@example.com",
                        first_name: "John", last_name: "Smith",
                        password: "foobar", password_confirmation: "foobar",
                        email_confirmation: "user@example.com") }

您是否真的打算将电子邮件确认保存在数据库中，或者您只是想在保存之前检查它是否与电子邮件匹配？我假设是后者，Rails 实际上已经内置支持这样做：

class User < ActiveRecord::Base
  validates :email, :confirmation => true
  validates :email_confirmation, :presence => true
end

在Rails Guide to Validations或validates_confirmation_ofAPI 文档中查看更多详细信息。（你可能需要为 . 做同样的事情:password_confirmation。）

于 2013-04-17T04:04:53.923 回答
27

刚刚花了很多时间调试我自己的这个实例，我想我会加入第三种可能性。

ActiveRecord我已经正确完成了迁移，并通过在 rails 控制台中检查我的来验证它。我曾多次尝试从架构中重新创建数据库，并且多次尝试重新运行迁移，但均无济于事。

就我而言，问题是我在运行单元测试时看到了问题，而不是在运行时。问题是我的测试数据库在我的迁移/回滚测试中不同步。解决方案非常简单。我所要做的就是重置测试数据库：

rake db:test:prepare
于 2016-09-09T13:39:30.893 回答
11

我知道上面的答案被标记为正确并解决了 OP 的问题。但是这个错误还有另一个原因，在关于这个主题的许多 stackoverflow 帖子中都没有引起注意。当您忘记将 as: 选项用于 has_many 时，此错误可能发生在多态多态中。例如：

class AProfile < ActiveRecord::Base
  has_many :profile_students
  has_many :students, through: :profile_students
end

class BProfile < ActiveRecord::Base
  has_many :profile_students
  has_many :students, through: :profile_students
end

class ProfileStudent < ActiveRecord::Base
  belongs_to :profile, polymorphic: :true
  belongs_to :student
end

class Student < ActiveRecord::Base
  has_many :profile_students
  has_many :aprofiles, through: :profile_students
  has_many :bprofiles, through: :profile_students
end

这会给你这个错误：

Getting “ActiveRecord::UnknownAttributeError: unknown attribute: profile_id

当您尝试执行以下操作时：

a = AProfile.new
a.students << Student.new

解决方案是将 :as 选项添加到 AProfile 和 BProfile：

class AProfile < ActiveRecord::Base
  has_many :profile_students, as: :profile
  has_many :students, through: :profile_students
end

class BProfile < ActiveRecord::Base
  has_many :profile_students, as: :profile
  has_many :students, through: :profile_students
end
于 2014-12-15T23:45:56.103 回答
6

我有同样的问题，这就像魔术一样。在要更新的每个模型的迁移语句末尾添加此行。重置有关列的所有缓存信息，这将导致它们在下一次请求时重新加载。

    <ModelName>.reset_column_information

参考：https ://apidock.com/rails/ActiveRecord/Base/reset_column_information/class

于 2018-04-16T15:59:29.097 回答
0

当表格没有列时，我多次遇到此错误，但这次我有奇怪的原因。出于某种原因，我的迁移很完美，但（奇怪的是）schema.rb没有更新，所以rake db:migrate db:seed没有创建专栏。我不知道为什么会这样。

TL;DR，如果您的迁移是最新的，请检查schema.rb并确保它也是

于 2020-11-17T07:16:21.997 回答
-1

我有相同的消息错误，我修复了将参数排序为数据库中列定义的相同顺序：

控制器

def create
    worktime = Worktime.create(name: params[:name], workhours: params[:workhours], organization: @organization, workdays: params[:workdays])

    render json: worktime
end

数据库

Table: worktimes
Columns:
id  int(11) AI PK
name    varchar(255)
workhours   text
organization_id int(11)
workdays    text
于 2015-07-29T13:52:59.127 回答