On Thu, May 11, 2017 at 8:25 AM, Ilya Kaplan <kaplan.i...@gmail.com> wrote:
> Appreciate the advice, but it doesn't solve the problem. When you deploy to > the "global" staging, you'd still have same problem. Is "structure.sql" (I've never even heard of it until now) generated from the DB via migrations like schema.rb? If so, I don't see how you can have migration conflicts unless your developers are pushing untested code, in which case all bets are off... -- Hassan Schroeder ------------------------ hassan.schroe...@gmail.com twitter: @hassan Consulting Availability : Silicon Valley or remote -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CACmC4yDB8BrXPkn9y%2Bn6%3D5oD3hM84bGOZhgBqwO7Q7KnTcHA6A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
