Hello all,
I have a problem with migrations.
It looks like there is a constraint on developers to use the same DB during
the development process if they want to benefit from migrations.
Here''s an example.
There are 2 developers working on a project, each using his own DB server.
The first developer has created a project and a set of migrations.
db/migrate/001_initial.rb
db/migrate/002_some_test.rb
At this stage the schema_info is set at 2.
The first developer commits the code to svn and continues to
work.
The next day he creates another migration:
db/migrate/003_some_other_migration.rb
The second developer updates the code from svn and gets:
db/migrate/001_initial.rb
db/migrate/002_some_test.rb
He runs rake migrate and has schema_info version set to 2.
He decides to add a new migration (script/generate migration my_migration)
db/migrate/003_my_migration.rb
He commits the code to svn. The repository now has these files.
db/migrate/001_initial.rb
db/migrate/002_some_test.rb
db/migrate/003_some_other_migration.rb
db/migrate/003_my_migration.rb
This obviously is wrong , rake migrate fails
(comparison of Array with Array failed)
and I have obviously missed something very important in this process.
The only thing that comes to my mind, is that all the developers must use
the same physical DB.
Any hints ?
Thanks
--
Karol Hosiawa
_______________________________________________
Rails mailing list
Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
http://lists.rubyonrails.org/mailman/listinfo/rails