Wouldn't be a viable solution for an old project I was working on: we had to support different SQL back ends.
Liquibase abstracts it away and allows you to use plain SQL where you need it. Your solution looks simple at first glance, but does not scale very well. For small projects your approach will work, but its an instance of "not invented here".
> Then spends two days fiddling with config files to get it working.
Not really the case in the project I've used liquibase with.
Liquibase abstracts it away and allows you to use plain SQL where you need it. Your solution looks simple at first glance, but does not scale very well. For small projects your approach will work, but its an instance of "not invented here".
> Then spends two days fiddling with config files to get it working.
Not really the case in the project I've used liquibase with.