why we use abstract_class in active_record ?

最新推荐文章于 2017-02-07 11:37:00 发布

up2u0609

最新推荐文章于 2017-02-07 11:37:00 发布

阅读量101

点赞数

分类专栏： "ruby" + " on rails" * rand(2) 文章标签： AIR ActiveRecord Rails

本文链接：https://blog.csdn.net/up2u0609/article/details/83498090

版权

"ruby" + " on rails" * rand(2) 专栏收录该内容

13 篇文章 0 订阅

订阅专栏

in the sample below:
class BookLib < ActiveRecord::Base
self.abstract_class = true
end
since abstract_class is set to true, this model class shifts to be a fade one(no table will be create for it), why we need a fade model in our project? yeah , we do need, it's powerful air in some cases.
let's assume a situation: we gonna request a batches data of book, the problem is these data were stored into another independent db. so how we touch them in our project.
let's do it like these:
class BookLib < ActiveRecord::Base
self.abstract_class = true
establish_connection("db_#{RAILS_ENV}".to_sym)

validates_presence_of :name
end
class BookTag < BookLib; end
class Book < BookLib; end
in these way, when we gonna CRUD booktag and book , the project will establish connection first.