Supporting registry schema versioning and programmatic upgrade with a framework like liquibase

[Saravanan Raju]

Currently, all the necessary schema migrations are kept in one file and it is entirely composed of "create" statements. Instead of this approach, if we should consider breaking down each SQL statements into their respective files and use a framework like liquibase to do SQL migration. With this approach, any new changes that have to be introduced to the SQL entities could be versioned and could be applied on top of an existing database depending upon how far behind the existing database from the latest version.

[Harsha Chintalapani]

This sounds good to me and will be helpful during the upgrades. +1.