Background
Our database schema is managed via SQL scripts and Hibernate configuration files. This means our database is hard to refactor. Consequently, it accumulates (and has accumulated) a lot of cruft.
We want to make it easier to refactor. To do this, we need a proof of concept for using Liquibase in our project. Liquibase is a tool that enables easy database refactoring, and allows us to keep our schema in a single, easy to understand, database independent format.
A complete proof of concept would demonstrate:
- Generating the database schema using Liquibase instead of SQL scripts
- Using Liquibase from Maven, instead of running SQL from Maven
- Having a process for updating Hibernate configurations - this can be a manual process, but needs to be documented.
- Integrating with our existing database upgrade mechanism - code modifications may be needed here.
- Ideally, we'd have a documented process for making a database change, that included: _ Updating Liquibase files _ Updating Hibernate configurations * Creating a Java database upgrade (or having this done automatically somehow)
Status - Active
Contact
Please email the mifos-developer list if you are interested in helping on this project.
Mentor
Current Volunteer(s)
Ravi Chinoy
Time Estimate
30 hours
Prerequisite experience
Java, and SQL experience; Maven and Hibernate experience helpful.
Details
Steps
- Read the Developer Kick Start page for information on contributing and getting set up. Follow the steps under
- Introduce yourself to the community - Mailing Lists
- Fill out the Contributor Agreement
- Set up your machine for development:
- Read how to submit patches
- Discuss your ideas for accomplishing this on the Mifos developer list - we're happy to help!