Hi there,
Just wondering how others deal with team development when several groups are tweaking the db across different branches.
I guess not checking in migrations could help. A downside is the time now required for each dev to get the db working on each merge.
There’s an interesting article from the rails community where they check in multiple versions of their actual (sqlite) db, each with a branch specific name: Enhancing your Rails app with SQLite | Fractaled Mind
The above appeals as the checked in db could have prefilled in dummy data and accounts.
Anyone doing this in Django land? Cheers, Andy
In our specific case, each developer is responsible for merging from master to their working branch on an as-necessary basis before merging their branch into master. Admittedly, it’s a bit of a hassle at times, but it works for us. (We’re a small-enough team to know when changes are being made that might affect each of us so it generally ends up being not too bad.)
That would be interesting for our projects using sqlite. I can see some value to this. Thanks for the reference!
But most of our projects are using PostgreSQL, so we develop using PostgreSQL as the target database. There are too many differences between them to develop on one only to deploy to the other.