Skip to content

Conversation

agent-z28
Copy link

No description provided.

@pedrobaeza
Copy link
Member

Can you explain why it shouldn't exist?

@MiquelRForgeFlow MiquelRForgeFlow added this to the 15.0 milestone Sep 25, 2025
@agent-z28
Copy link
Author

@pedrobaeza
I just happend that me and @PCatinean had the Problem in completely diffrent databases and systems.
When he told me that he had the same problem, i just thought it would be nice to share the fix.

Also i'm aware that the field is there in:
https://github.com/odoo/odoo/blob/14.0/addons/project/models/project.py#L603

Maybe it happens when the OpenUpgrade get's started a second time for the same version.

@pedrobaeza
Copy link
Member

Well, it we don't know the reason/root, it's hard to determine if this is the proper solution. For now, this is only omitting a renaming of a column, but maybe it's because the existing column coming from other module that is adding it, and contains incorrect data, and then the problem is at another level. Do you understand my point?

@agent-z28
Copy link
Author

@pedrobaeza Yes, I understand.
The idea was simply to check if the column exists first, and then proceed with the rename — this ensures the operation runs correctly every time.

@PCatinean did you find anthing more ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants