On Wed, Jun 11, 2014 at 10:29 AM, Ivailo Bardarov <[email protected]> wrote:
I see your point that Rails is following the STI pattern. > However I can't see why the column should be static in the schema and not > to use the virtual one. I will have to spare some time to work on this to > find out whats going to happen. > I would suggest a change of perspective, really. Your application is not using a "dynamic STI". It is using Postgres true table inheritance. Everything is different, tables are different, attributes are different, queries are different. In my view, it makes no sense to hack STI in AR to be able to support something that is not STI. Instead of doing that, it would be better to implement support for Postgres table inheritance as is. The abstractions and API should reflect Postgres table inheritance. -- 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.
