-
Notifications
You must be signed in to change notification settings - Fork 70
[IMP] util/models: check m2m tables on model rename #278
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
Conversation
ca53be3
to
edc0489
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.
First quick review.
bb4bd77
to
5113080
Compare
upgradeci retry |
upgradeci skip |
upgradeci retry with always * in versions 10.0 11.0 12.0 saas~12.3 13.0 14.0 15.0 16.0 17.0 18.0 |
0b51946
to
bbb6a54
Compare
upgradeci retry |
bbb6a54
to
3a9aa15
Compare
3a9aa15
to
58bd009
Compare
upgradeci retry with only base_sparse_field in 15.0 |
upgradeci retry |
upgradeci retry with * in all versions |
58bd009
to
5e9ae34
Compare
upgradeci skip |
5e9ae34
to
1cebacf
Compare
1cebacf
to
8837b07
Compare
The
|
f11d163
to
9c8a2b0
Compare
d3829d2
to
7fb14dc
Compare
|
7fb14dc
to
2eb97b9
Compare
When renaming a model we need to check m2m tables that may need to be renamed as well. Otherwise the ORM will create a new table that would be empty. If the data is handled directly in the scripts the ignore parameter can be used to avoid warnings. Notes: * As this is a breaking change, this only done by default from Odoo saas~18.1 * From Odoo 9 the column relation_table exists in ir_model_fields * From Odoo 10 the name of m2m tables is given by the model names ordered alphabetically Related: odoo/upgrade#7752
2eb97b9
to
74826f6
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.
@robodoo r+
When renaming a model we need to check m2m tables that may need to be renamed as well. Otherwise the ORM will create a new table that would be empty. If the data is handled directly in the scripts the ignore parameter can be used to avoid warnings. Notes: * As this is a breaking change, this only done by default from Odoo saas~18.1 * From Odoo 9 the column relation_table exists in ir_model_fields * From Odoo 10 the name of m2m tables is given by the model names ordered alphabetically closes #278 Related: odoo/upgrade#7752 Signed-off-by: Christophe Simonis (chs) <[email protected]>
When renaming a model we need to check m2m tables that may need to be renamed as well. Otherwise the ORM will create a new table that would be empty. If the data is handled directly in the scripts the ignore parameter can be used to avoid warnings. Notes: * As this is a breaking change, this only done by default from Odoo saas~18.1 * From Odoo 9 the column relation_table exists in ir_model_fields * From Odoo 10 the name of m2m tables is given by the model names ordered alphabetically closes #278 Related: odoo/upgrade#7752 Signed-off-by: Christophe Simonis (chs) <[email protected]>
When renaming a model we need to check m2m tables that may need to be
renamed as well. Otherwise the ORM will create a new table that would be
empty. If the data is handled directly in the scripts the ignore
parameter can be used to avoid warnings.