Task #12260 (new)
Opened 10 years ago
Last modified 8 years ago
RFE: database script upgrade schema comparison
| Reported by: | mtbcarroll | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | Model | Version: | 5.0.1 |
| Keywords: | n.a. | Cc: | jamoore, ajpatterson, sbesson, pwalczysko |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Perhaps another check that can be done for breaking PRs, perhaps even by CI, is to compare the dump (including full schema) of a database set up fresh from bin/omero db script with one set up fresh from a rather older version then upgraded. (That the server starts up is perhaps insufficient verification that the upgrade scripts work correctly.) There would probably have to be a little latitude for case, whitespace, ordering, etc. in the dump comparison though.
(This was a standard step of upgrade script QA where I last worked.)
Change History (2)
comment:1 Changed 10 years ago by jamoore
comment:2 Changed 8 years ago by jamoore
- Cc changed from jamoore,ajpatterson,sbesson,pwalczysko to jamoore, ajpatterson, sbesson, pwalczysko
- Milestone set to Unscheduled
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
I've previously done this manually with APG. +1 for doing it automatically.