I'm trying to find the "Rails way" of modeling users of my
application. Traditionally, I'd have a "users" table with common
information, along with "students" and "teachers" tables. For login
purposes, I'd only be concerned with the users table. (Classic class
table inheritance, basically.)
Since Rails supports single table inheritance, how would the Rails
gurus model this app? Is it really best to just throw everyone into
one "users" table, and have a load of columns on it?
Any input will be appreciated!