- Mailing Lists
- Contributors
- Migration 12.0 -> 13.0 and field collision
Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
Re: Candidature pour un poste en Alternance – Bachelor Concepteur développeurd’applications
Re: pre-commit changes
Migration 12.0 -> 13.0 and field collision
Hi,
I'm starting a migration process for a copy of our production database and it fails on the following error (detailed log attached):
ERROR mig_9008 odoo.sql_db: bad query:
UPDATE ir_model_fields
SET name = 'notified_partner_ids'
WHERE name = 'needaction_partner_ids'
AND model = 'mail.message'
UPDATE ir_model_fields
SET name = 'notified_partner_ids'
WHERE name = 'needaction_partner_ids'
AND model = 'mail.message'
ERROR: duplicate key value violates unique constraint "ir_model_fields_name_unique"
DETAIL: Key (model, name)=(mail.message, notified_partner_ids) already exists.
DETAIL: Key (model, name)=(mail.message, notified_partner_ids) already exists.
ERROR mig_9008 OpenUpgrade: mail: error in migration script mail/migrations/13.0.1.0/pre-migration.py: duplicate key value violates unique constraint "ir_model_fields_name_unique"
I tracked down the issue and I found out that the `notified_partner_ids` field was an existing field added in 7.0 but deleted in 9.0.
Maybe this field should have been dropped or renamed to `openupgrade_legacy_xxx`, I don't know if it should be the case or if I made a mistake in my original upgrade path, but this field still exists in our database even if not referenced in any files.
Whatever, if you are in my case, I made a PR to identify and remove orphaned fields (for the database_cleanup module):
For the record, we have more than 1000 orphaned fields (list attached) in our production database (updated from 6.1 -> 7.0 -> 8.0 -> 9.0 -> 10.0 -> 11.0 in october 2020)
--
|
Yann PAPOUIN Ingénieur R&D |
|
||||||||||||||||
|
||||||||||||||||||
![]() |
by Yann Papouin - 11:46 - 6 Dec 2022

