Can someone explain why you would expect to see schema.rb conflicts if the checked in migrations are in sync with the checked in schema.rb? Wouldn't you expect cruise to generate a schema.rb identical to the one checked in?
On Fri, May 2, 2008 at 2:44 AM, Jeremy Stell-Smith < [EMAIL PROTECTED]> wrote: > it's still a generated file, and will still introduce conflicts on a system > like cruise if you're running migrations on said system - because each time > you do, it will regenerate a new copy of the file.
_______________________________________________ Cruisecontrolrb-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
