-
-
Notifications
You must be signed in to change notification settings - Fork 706
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
[17.0][OU-ADD] account: Migration to 17.0 #4668
base: 17.0
Are you sure you want to change the base?
Conversation
/ocabot migration account |
tests are fixed in #4669, which also actually makes the files from the test folder run |
/ocabot rebase |
3322759
to
d16d0b3
Compare
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.
Tested and so far seems OK
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.
I tested it, and it's working fine. This PR is blocking several others. Could it be prioritized? @pedrobaeza
def convert_from_company_dependent( | ||
env, | ||
model_name, | ||
origin_field_name, | ||
destination_field_name, | ||
origin_id_column_name, | ||
model_table_name=None, | ||
): | ||
""" | ||
Move a company-dependent field back to the model table. |
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.
I think it could be useful to move this function to openupgradelib
to improve reusability. It could serve as a base utility for scenarios requiring the conversion of property fields to JSON during migrations to version 18.
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.
that's a very different logic, you'll find the v18 function here
By now I've seen most of the migrations for v17 and didn't see another module where the case we have in the account module happens.
This PR has the |
continuation of #4662
I tested this with my own DB, a few customers', and the demo database and couldn't find issues any more, so from my side I think it's done.