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
[FIX] fix perf issue with sale_order_lot_selection #275
[FIX] fix perf issue with sale_order_lot_selection #275
Conversation
('id', 'child_of', location.id), | ||
]) | ||
# Search all lot existing lot for the product and location selected | ||
self._cr.execute("""SELECT lot_id |
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.
You can use quants for searching, but without SQL. The performance will be for sure still good. You can use read_group function if you want to increase it. This way, you don't overpass multi-company rules, and so on.
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.
good idea, let's fix it
ef29da6
to
b626fed
Compare
b626fed
to
119a5ba
Compare
@pedrobaeza everything is green and use read_group ;) |
Thanks 👍 |
👍 |
👍 |
…der-lot-selection [FIX] fix perf issue with sale_order_lot_selection
Thanks 😄 |
Really Thank You @sebastienbeau 👍 |
Hi, first thank to Agilebg for this module
I have some perf issue with sale_order_selection_lot. Indeed my customer have more than 4000 lot for a product and when he try to select it in a sale order the function spend 3 min to compute the lot available.
With this change it spend less than 0,023s
What do you think?
@hurrinico @eLBati
Thanks for you're feedback