Skip to content
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

Add the ability to upgrade 2.5 -> 3.3 #1141

merged 3 commits into from May 30, 2019


None yet
3 participants
Copy link

commented Dec 13, 2018

So far as I can tell, no DB schema changes occur all the way from 2.5 up until 3.3. I have added an
init330() function which generates the SQL commands described in the changelog, which should allow the user to upgrade directly from 2.5 -> 3.6.

I'd be happy to add some tests for this if I could get some direction as to how to initialize the db in a 2.5 state. I've also added the appropriate versions to the VersionEnum.


This comment has been minimized.

Copy link

commented Dec 13, 2018

Coverage Status

Coverage increased (+0.02%) to 74.58% when pulling 4fea74c on tadgh:upgrade-25-to-33 into 81e8131 on jamesagnew:master.

@jamesagnew jamesagnew merged commit b36e9dd into jamesagnew:master May 30, 2019

0 of 2 checks passed

continuous-integration/appveyor/pr Waiting for AppVeyor build to complete
continuous-integration/travis-ci/pr The Travis CI build is in progress

jamesagnew added a commit that referenced this pull request May 30, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.