gpt4 book ai didi

ruby-on-rails - SQLite3::ConstraintException:列电子邮件不是唯一的

转载 作者:太空宇宙 更新时间:2023-11-03 17:24:05 24 4
gpt4 key购买 nike

我对 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 目前默认为两个没有属性的灯具。如果您在测试环境中运行,那么这些固定装置将作为两条记录加载到测试数据库中,电子邮件为零值,这是重复的电子邮件值。像下面这样的固定装置会让您传递错误消息。

file: app/test/fixtures/users.yml

one:
email: user@example.com
encrypted_password: password1

two:
email: user2@example.com
encrypted_password: password2

关于ruby-on-rails - SQLite3::ConstraintException:列电子邮件不是唯一的,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/19364622/

24 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com