我绝对是Rails的新手,我几乎不知道我在做什么。但。问题是:使用 Devise 注册新用户会导致:
SQLite3::ConstraintException: column email is not unique:
INSERT INTO "users" ("created_at","encrypted_password", "name", "updated_at")
VALUES (?, ?, ?, ?)
和请求参数:
{"utf8"=>"✓",
"authenticity_token"=>"1bgk4ovS3JitphVkIvcCZi3ex8QsBq4eEf6ZihQLiHg=",
"user"=>{"name"=>"Someone",
"email"=>"8@prosto.me",
"password"=>"[FILTERED]"},
"commit"=>"Sign up"}
用户型号:
class User < ActiveRecord::Base
# Include default devise modules. Others available are:
# :token_authenticatable, :confirmable,
# :lockable, :timeoutable and :omniauthable
devise :database_authenticatable, :registerable,
:recoverable, :rememberable, :trackable;
end
数据库迁移:
class DeviseCreateUsers < ActiveRecord::Migration
def self.up
change_table(:users) do |t|
## Database authenticatable
t.string :email, :null => false, :default => ""
t.string :name, :null => false, :default => ""
t.string :encrypted_password, :null => false, :default => ""
## Recoverable
t.string :reset_password_token
t.datetime :reset_password_sent_at
## Rememberable
t.datetime :remember_created_at
## Trackable
t.integer :sign_in_count, :default => 0
t.datetime :current_sign_in_at
t.datetime :last_sign_in_at
t.string :current_sign_in_ip
t.string :last_sign_in_ip
## Confirmable
# t.string :confirmation_token
# t.datetime :confirmed_at
# t.datetime :confirmation_sent_at
# t.string :unconfirmed_email # Only if using reconfirmable
## Lockable
# t.integer :failed_attempts, :default => 0 # Only if lock strategy is :failed_attempts
# t.string :unlock_token # Only if unlock strategy is :email or :both
# t.datetime :locked_at
## Token authenticatable
# t.string :authentication_token
# Uncomment below if timestamps were not included in your original model.
# t.timestamps
end
add_index :users, :email, :unique => true
add_index :users, :name, :unique => true
add_index :users, :reset_password_token, :unique => true
# add_index :users, :confirmation_token, :unique => true
# add_index :users, :unlock_token, :unique => true
# add_index :users, :authentication_token, :unique => true
end
def self.down
# By default, we don't want to make any assumption about how to roll back a migration when your
# model already existed. Please edit below which fields you would like to remove in this migration.
end
end
请告诉我是否需要提供任何其他代码。并提前感谢您的所有帮助。
使用数据库架构更新:
ActiveRecord::Schema.define(version: 20131012114812) do
create_table "users", force: true do |t|
t.string "email", default: "", null: false
t.string "encrypted_password", default: "", null: false
t.string "reset_password_token"
t.datetime "reset_password_sent_at"
t.datetime "remember_created_at"
t.integer "sign_in_count", default: 0, null: false
t.datetime "current_sign_in_at"
t.datetime "last_sign_in_at"
t.string "current_sign_in_ip"
t.string "last_sign_in_ip"
t.datetime "created_at"
t.datetime "updated_at"
t.string "name"
end
add_index "users", ["email"], name: "index_users_on_email", unique: true
add_index "users", ["reset_password_token"], name: "index_users_on_reset_password_token", unique: true
end
更新2:身份验证也存在问题。Devise 告诉任何以前成功注册的用户尝试登录的"无效电子邮件或密码"。
SQLite告诉你它正在尝试创建一个新记录,其中一个值将是电子邮件,但该电子邮件已经有一个现有记录。
读取数据库记录的一种简单方法是在终端窗口中查询数据库:
$ rails console
$ User.all
如果您想查看将随夹具一起加载的测试数据库:
$ rails console -e=test
$ User.all
查找与您尝试创建的电子邮件具有相同电子邮件的记录。
如果这是您第一次使用Devise,您应该检查您的灯具。Devise目前默认为两个没有属性的赛程。 如果您在测试环境中运行,则这些夹具将作为两条记录加载到测试数据库中,电子邮件值为 nil,这是重复的电子邮件值。 像下面这样的夹具会让你传递你的错误消息。
file: app/test/fixtures/users.yml
one:
email: user@example.com
encrypted_password: password1
two:
email: user2@example.com
encrypted_password: password2
该数据库中还有其他"电子邮件"列吗?
也许您已经有一个"用户"表,其中的电子邮件列已使用 Devise 复制。如果您能向我们展示您的表:)哪些列,那将很有帮助
尝试向User
模型添加唯一性验证:
validates_uniqueness_of :email, :allow_blank => true
这将重新呈现您的用户创建表单,而不是导致错误。