Handling schema changes when working with multiple feature branches

Question

Is there another way, or some tool, to handle database schema changes in multiple parallel feature branches other than creating a separate database for each one in development?

ie. Spin up a DB in memory based on some configuration or script and populate with DbUnit before running tests.

This question is specifically targeted at unit testing, but could be applicable to UAT as well.

score 3 · Answer 1 · answered Dec 06 '12 at 03:47

3

Have you looked at the H2 database engine? If you are using Spring, you might try the approach documented here: Unit Testing JPA with in-memory H2 database (useful info, even if not using Spring). A quick google search yielded this blog post, indicating there are definitely folks out there using H2 with DbUnit.

answered Dec 06 '12 at 03:47

kahowell

27,286
1
14
9

This sounds a bit promising. I'll do some research into it for now. – bvulaj Dec 06 '12 at 16:47

score 0 · Answer 2 · answered Dec 06 '12 at 04:05

We're using dbdeploy and it works extremely well for us. It helps manage db creation scripts in version control manner. It still needs a bit of work on top of it (eg. concurrent sql migration if application is deployed simultaneously on multiple nodes) but except this its works well out of the box.

score 0 · Accepted Answer · answered Apr 04 '14 at 20:21

0

After a long while, it seems like Liquibase, in conjunction with other tools like DbUnit, should be able to accomplish what I had originally asked.

Thanks for all of the other suggestions.

answered Apr 04 '14 at 20:21

bvulaj

5,023
5
31
45

Handling schema changes when working with multiple feature branches

3 Answers3