New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix #11516: add upgrade scripts from 4.4 to 5.0 #1691
Conversation
CONSTRAINT fkfilesetversioninfo_owner_id_experimenter FOREIGN KEY (owner_id) REFERENCES experimenter, | ||
CONSTRAINT fkfilesetversioninfo_update_id_event FOREIGN KEY (update_id) REFERENCES event | ||
); | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This commented-out part following is basically a way of skipping the usual fresh-install process in which we create these tables, then drop them, that allows us to remember what the tables actually would have been.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As mentinoed to @mtbc, these commented section is just a byproduct of Hibernate's SQL generation. It can be removed in the next PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed in #1723.
Looks good:
Browsing images, S/P/W and big image all seem to be fine after upgrade. |
fix #11516: add upgrade scripts from 4.4 to 5.0
--no-rebase |
A good way to test the upgrade may be to import some data into 4.4, actually do the upgrade, and see if the system still works okay. I tried to make the SQL scripts actually quite human-readable.
Fixes http://trac.openmicroscopy.org.uk/ome/ticket/11516.