the whole concept of the migration is the provide a common platform for Database to the entire team. so, yes we definitely commit them.
The DB in use local or test or production all have a table called migration(or something similar) which keeps the track which migrations have been run in that particular database. And the current state of DB is manipulated according to that only.
I am from PHP background so if you are using laravel or CakePHP they come with there Migration tools. In case you are using core PHP you can use the phinx for the migration. It's a great library.
In case you are using any other language, there must be some library available. have a look around.
the whole concept of the migration is the provide a common platform for Database to the entire team. so, yes we definitely commit them.
The DB in use local or test or production all have a table called migration(or something similar) which keeps the track which migrations have been run in that particular database. And the current state of DB is manipulated according to that only.
I am from PHP background so if you are using laravel or CakePHP they come with there Migration tools. In case you are using core PHP you can use the phinx for the migration. It's a great library.
In case you are using any other language, there must be some library available. have a look around.
thanks.
Thanks for your response. This really helped
any time brother.