Hello, is there something wrong with using has_one to implement Class
Table Inheritance ?
class Person < ActiveRecord::Base
attributes : eg. name, string
class Contact < Person
Of course for a such simple case I could use Single Table Inheritance
but this is only an example and I don’t like too much the fact of mixing
in a single table a bunch of inrelated and unused properties.
Your advice is welcome, thanks