has belongs charge churned databases
i have conditions where i have twin models, companies permissions, where companies removed database permissions database. belongs charge since any association have permissions any assent go companies.
the reason twin databases separate since association database runs high proceed prolongation concentration permissions database controls permissions another application.
with rails, looks join list same database primary table. instance, i company.permissions, looks association database company_permissions. i permission.companies looks permissions database.
what best fortitude controlling belongs charge churned databases?
Comments
Post a Comment