我需要对另一个数据库中的现有用户表使用Devise,所以我配置了database.yml:
development:
adapter: postgresql
encoding: unicode
database: almoxarifado
pool: 5
timeout: 5000
username: user
password: pass
host: localhost
users_development:
adapter: postgresql
encoding: unicode
database: portal
pool: 5
timeout: 5000
username: user
password: pass
host: localhost
schema_search_path: users
在我的模型中,我编写了以下代码:
class User < ActiveRecord::Base
establish_connection "users_#{Rails.env}"
devise :database_authenticatable, :registerable,
:recoverable, :rememberable, :trackable, :validatable
end
当我运行Railsc并调用模型类时,这工作得很好。
迁移文件:
class AddDeviseToUsers < ActiveRecord::Migration
def self.up
ActiveRecord::Base.establish_connection "users_#{Rails.env}"
change_table(:users) do |t|
## Database authenticatable
t.string :email, :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, :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
## 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, :null => false # Only if lock strategy is :failed_attempts
# t.string :unlock_token # Only if unlock strategy is :email or :both
# t.datetime :locked_at
# Uncomment below if timestamps were not included in your original model.
# t.timestamps
end
add_index :users, :email, :unique => true
add_index :users, :reset_password_token, :unique => true
# add_index :users, :confirmation_token, :unique => true
# add_index :users, :unlock_token, :unique => true
ActiveRecord::Base.establish_connection "#{Rails.env}"
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.
raise ActiveRecord::IrreversibleMigration
end
end
但是rake db:migrate返回此错误:
== AddDeviseToUsers: migrating =======================================
-- change_table(:users)
rake aborted!
An error has occurred, this and all later migrations canceled:
undefined method `rollback' for #<ActiveRecord::ConnectionAdapters::ClosedTransaction:0xbb06767c>
Tasks: TOP => db:migrate
(See full trace by running task with --trace)
6条答案
按热度按时间l7wslrjt1#
因为我花了很多时间尝试与所有的替代品在这和其他职位,没有成功,这里的解决方案,我的作品
数据库.yml
型号/您的型号.rb
您的迁移
**解释:**因为ActiveRecord::Base.establish_connection关闭了连接,所以我直接使用来自模型的连接。另外,因为我使用UUID和uuid_generate_v4()方法作为默认值,所以我使用相同的连接启用了扩展
fjnneemd2#
=========================更新===========
我找到一篇很好的文章谈论它:http://www.thegreatcodeadventure.com/managing-multiple-databases-in-a-single-rails-application/
=========================更新===========
我只是将establish_connection从迁移类中取出。
z31licg03#
在迁移类中创建方法
def self.connection ActiveRecord::Base.establish_connection("#{Rails.env}_yourcustomenv").connection end
我花了一些时间才意识到需要一个用self声明的方法,这在Rails4.0上是可行的
jslywgbw4#
你就快找到答案了。只需要做
User.connection
而不是ActiveRecord::Base.establish_connection
。看看这里的解决方案:https://stackoverflow.com/a/34292909/2499227
ActiveRecord::Base.establish_connection
方式总是给我带来schema_migrations和/或连接关闭的问题,但是Model连接运行得很顺利。disbfnqx5#
在您的配置文件/database.yml中:
在路径config/initializers/中创建一个包含此内容的文件:
然后在迁移文件中继承它:
ukxgm1gy6#
使用了一个简单一点的方法,它对我来说在Rails6上工作。
还有模特...