-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
support upgrading from 5.0 schemas #52
base: main
Are you sure you want to change the base?
Conversation
Current problem: chicken/egg with the new columns in the profiles table
|
Fixed the previous errors. now we have
|
ok, worked past those. now we're at this error
|
the previous error has a very reasonable fix. But now we're left with this.
|
trying each constraint in isolation is fun.
|
c3f30ab
to
f0bdc2c
Compare
Holy crap, checksetup completes without error. |
Does that mean this is ready to go? |
Thanks! The first commit seemed incomplete, I needed 0c67afe to get the process to complete. |
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.
Works for me :)
Setting this back to draft, as a) what's here won't merge cleanly anyway, and b) the demo @dylanwh just showed me still breaks on the keyworks table, so I know it's WIP still anyway. |
How would one reproduce this problem? |
@dylanwh if you're around Sunday afternoon, let's play with this. |
Please :) |
Details
We need to tweak the schema migration code to support coming from 5.0.
Additional info
Test Plan
Start with a 5.0 database dump.
Run checksetup.pl
the result should be a working bugzilla install