How to organize database data synchronization between developers during the development period?

Question

MySQL

The issue of code relevance for all developers is solved by version control systems.
Integrity of the database structure by migrations.
But what about the data?
Well, the developer has made a new feature. In the process of testing, he created a certain number of records in the database. Some new objects and a bunch of replicated data.
If he just pushes his codes, then no one will see his feature.
What tools are available to solve this problem?

Answer 1

And what prevents you from adding data to the migration?

Answer 2

Seeds are used to populate the database with test data. Only their code is written in such a way that they do not just try to put data into the database, but before that look for similar ones. If the data is too complex - the same seeds, but the values ​​themselves are stored in YML files in some db/fixtures folder.
If this is not enough, you can look towards https://github.com/harrystech/seed_migration
. You can also write rake tasks like db:populate:feature_name - this approach will allow you to fill the database with only the necessary data. Well, accordingly, there will be one common task that will drive all populate

Answer 3

well pushte at the same time and insert scripts. Replication, something tells me, it will only interfere here.

Answer 4

Use seeds.rb, not migrations. Since the migrations will have to be run on the production server, and your task is to exchange data only among developers.