ruby on rails - Devise implementation. Admin as a separate table or as a column -
ruby on rails - Devise implementation. Admin as a separate table or as a column -
may question theoretical, know sentiment on usage of devise separate table, or column in users table.
some basic point great discuss: 1. in situation take or other implementation? 2. methods devise add together when implementing seperate table? 3. find easiest way implement devise, , why?
thank in advance
sure can 2 or more devise model in each application.
but in many case 'single table inheritance(sti)' might help lot. if info not different , have same behavior. create easy handle complex info sometimes.
but there create lot of null column in table when each role store different info , have slower query time.
if want customize much more role can devise cancan help life easier.
ps. in real life normalized info not mean have database design.
ruby-on-rails devise theory
Comments
Post a Comment