Downloads Documentation Community Contribute Demo






Show Sidebar
Login | Register

Ticket #974 (closed enhancement: fixed)

Opened 2 years ago

Last modified 1 year ago

OpenMRS database auto update using Liquibase

Reported by: upul Assigned to:
Priority: major Milestone: OpenMRS 1.5
Component: OpenMRS Code Base Keywords:
Cc: jmiranda Introductory Ticket: 0
Code Review Status:

Description

This is a tentative patch. OpenMRS web application calls the Liquibase programatically at startup. It will read the database changes from an XML file and mark the performed database changes in a dedicated table. This works in a similar manner to how the database updates are done in the OpenMRS modules at present.

This will eliminate the step where the user has to run the update-to-latest-db.mysqldiff.sql SQL script using the mysql client program in a shell. And it is database server type independent. Also this eliminates the dependence on mysql client program.

Attachments

openmrs-974-liquibase-1.patch (8.6 kB) - added by upul on 08/13/08 17:42:40.
openmrs-974-liquibase-1.2.patch (8.9 kB) - added by upul on 08/13/08 18:43:35.

Change History

08/13/08 17:42:40 changed by upul

  • attachment openmrs-974-liquibase-1.patch added.

08/13/08 18:43:35 changed by upul

  • attachment openmrs-974-liquibase-1.2.patch added.

11/26/08 16:15:47 changed by bwolfe

  • intro_ticket changed.

I've committed changes in [6122] to the http://dev.openmrs.org/browser/openmrs/branches/ticket974-liquibase/ branch.

This built off of what Upul did and expanded it to include a startup wizard for creating the database. Its a simpleton wizard that will need a lot of cleanup.

There are several minor TODOs within the code that we will want to implement eventually.

01/02/09 16:57:47 changed by bwolfe

  • cc set to jmiranda.
  • review_status changed.
  • status changed from new to closed.
  • resolution set to fixed.
  • milestone set to OpenMRS 1.5.

It seems the changes discussed in the code review of this a few weeks back never made it to the ticket. Nevertheless, the changes were committed to the branch.

The branch has been merged to trunk. See [6505] and [6506]. There are several tickets for some clean up work that need to be done before 1.5 is eventually released: #1187, #1188, #1189, #1190