Single table inheritance is generally a bad pattern, and leads to all kinds of nasty rabbit holes like the ones you are describing.
I generally avoid STI in almost all cases because of the overhead (it is generally not efficient from data base perspective) and all the callback woes you are describing are a good case in point for moving away from that style of programming entirely. On Aug 27, 2014, at 5:43 PM, Anthony Cameron <[email protected]> wrote: > Would love to hear thoughts on the matter, or patterns that make it feel less > cumbersome to accept nested attributes for a STI class -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
