Skip to content

Conversation

@qgroulard
Copy link
Contributor

This field is often searched which may be slow on DB with a lot of account moves.

This field is often searched which may be slow on DB with a lot of account moves.
Copy link
Member

@flotho flotho left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code review,
LGTM
Great thanks

Copy link
Member

@FrancoMaxime FrancoMaxime left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@pedrobaeza pedrobaeza added this to the 18.0 milestone Nov 10, 2025
@pedrobaeza
Copy link
Member

There's only one search:

invoices |= self.env["account.move"].search([("old_contract_id", "=", self.id)])

and that one is only for retro-compatibility with 11-. I'm wondering if we should still provide that compatibility...

@qgroulard
Copy link
Contributor Author

There's only one search:

invoices |= self.env["account.move"].search([("old_contract_id", "=", self.id)])

and that one is only for retro-compatibility with 11-. I'm wondering if we should still provide that compatibility...

I agree we should consider removing this feature.

@pedrobaeza
Copy link
Member

Go ahead then.

@pedrobaeza
Copy link
Member

The field hasn't been removed as talked.

@qgroulard
Copy link
Contributor Author

That's still on my todo list but the go-live of a major customer in a few days leaves me little time.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants