> On Jan 26, 2015, at 11:49 AM, Jason Fleetwood-Boldt <t...@datatravels.com> > wrote: > > If I were you I’d stub out all the different objects with ‘shell’ > implementations in your master branch, and then AR won’t blow up when it > tries to instantiate the objects. Then you can leave implementation details > to the branches where you want to implement/test them.
Yeah, this is one of a few possible workarounds, but very inconvenient for us. > Are all those objects different from eachother? (That is, do they each > implement a certain domain logic that can best be implemented with Ruby code). Yes, that's exactly the case. >> On Jan 26, 2015, at 6:24 AM, Xavier Noria <f...@hashref.com >> <mailto:f...@hashref.com>> wrote: >> >> You're facing one possible way to have incompatible schemas between branches. >> >> Divergence in Git branches is an external issue, and should be solved where >> it is originated in my view, at the workflow level. >> >> If your application has a very specific use case for STI it could be the >> case that your most efficient way to workaround it is by monkey patching >> something in AR... that depends on the details. But certainly I don't see >> the solution builtin in AR. Is it really an “incompatible schema”-type problem when in fact it’s certain db records (data) that cause errors, not the schema itself? The way I see this: rails has default behavior for dealing with type column (it constantizes it), and this behavior could be easily swapped if given a hook. However, your main argument (i.e. it’s a workflow problem) does sound pretty convincing, especially given the vibe I’m getting that I’m the only one who needs this so far, so I don’t want to impose. -- 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 rubyonrails-core+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
