Odoo Changelog — 2025-12-09

Tuesday, December 9, 2025

3 changes

Refactoring(3)

Code cleanup and technical improvements

The Blip

Enterprisemasterenterprise

This update streamlines Odoo's database queries by removing inefficient dynamic SQL usage. This change focuses on optimizing performance and reducing potential database load, leading to faster application response times. It's a technical update designed to enhance the overall stability and speed of the Enterprise edition.

Original PR description

Removes most / all dynamic SQL queries which don't use the `SQL` wrapper or misuse it.

#performance#database#optimization

[REF] knowledge: use Dropdown component for dropdown menus

PR #33905

Enterprisemasterknowledge

This update replaces the Knowledge dropdown menus with a standardized Odoo component, resulting in a more stable and consistent user experience. By leveraging this component, we've reduced development effort and simplified maintenance for these menus.

Original PR description

For the dropdown menus of Knowledge, we used the standard dropdown menus of Bootstrap. It turns out that there exists a Dropdown component in owl that we can use to create a dropdown menu. Using that component will offer the following advantages:
- With the component, the content of the dropdown menu will be lazy loaded. It means that we no longer have to re-implement that mechanism in our component. We can therefore reduce the amount of custom code.
- The structure of the dropdown menu is simplified. We will not necessarily have to update our component if the layout of the dropdown menu changes. The dropdown menu will always be consistent with the other dropdown menus of Odoo (given that everyone uses the Dropdown component).
- The dropdown menu can easily be customized.
- The display is less glitched.

task-3072845

#UI#dropdown#performance

[REF] pos_iot: move scales logic to enterprise

PR #101307

Enterprisemasterpos_iot

This update consolidates IoT scale logic within the dedicated `pos_iot` module for better organization. It also streamlines the scale functionality by transitioning from a service to a utility class, mirroring best practices for printers. This change enhances the overall consistency and maintainability of the point-of-sale system.

Original PR description

To maintain consistency, we moved IoT connected scales logic from `point_of_sale` to `pos_iot`.

We also switched from a service to an utility class, same as printers.

see odoo/odoo#238635

#pos#iot#scales#odoo

For the dropdown menus of Knowledge, we used the standard dropdown menus of Bootstrap. It turns out that there exists a Dropdown component in owl that we can use to create a dropdown menu. Using that component will offer the following advantages: - With the component, the content of the dropdown menu will be lazy loaded. It means that we no longer have to re-implement that mechanism in our component. We can therefore reduce the amount of custom code. - The structure of the dropdown menu is simplified. We will not necessarily have to update our component if the layout of the dropdown menu changes. The dropdown menu will always be consistent with the other dropdown menus of Odoo (given that everyone uses the Dropdown component). - The dropdown menu can easily be customized. - The display is less glitched. task-3072845