Odoo Changelog — 2026-05-15

Friday, May 15, 2026

3 changes · 19.0

Improvements(3)

Enhancements to existing features

[PERF] account: avoid `action_undo_reconciliation` when nothing to do

Core19.0account

Accounting line updates now skip unnecessary reconciliation checks when there is nothing to undo. This reduces avoidable database work and can make routine accounting updates faster without changing user-facing behavior.

Original PR description

Since `write` is often done record by record because the values written are different on all lines, the call to `action_undo_reconciliation` is actually not batched. Even if there is nothing to do, some queries are still done to make sure that there is nothing to do...

#performance#accounting#reconciliation

[IMP] safe_eval: bubble up `IntegrityError`

PR #264266

Core19.0base

Automated code execution now lets certain database conflict errors pass through so the system can retry them correctly. This makes behavior more consistent and can reduce avoidable failures when temporary database constraints or concurrency issues occur.

Original PR description

It makes sense to bubble up the `psycopg2.IntegrityError` (as well as
the subcase `ConcurrencyError`) so that the retry mechanism can handle
this exception.
In fact, this exception can be triggered without necessarily a problem
with the "logic/business code".

This ensures consistent behavior between the business logic and the code
executed in `safe_eval`.

Task-6215886

#safe_eval#reliability#retry

[IMP] account_reports: Align report subheader with report column

PR #116578

Enterprise19.0account_reports

This update aligns report subheaders and numeric data within reports to create a more consistent and professional appearance. Previously, the formatting was inconsistent, with subheaders centered and data aligned differently. This change ensures a uniform look across all reports, enhancing readability and user experience.

Original PR description

Before this commit, subheaders of numeric columns were centered, while the figures in the columns were aligned to the end. This commit ensures that both the subheader and the figures are aligned the same way (center or end).

task-6197223

#reports#formatting#user experience

Since `write` is often done record by record because the values written are different on all lines, the call to `action_undo_reconciliation` is actually not batched. Even if there is nothing to do, some queries are still done to make sure that there is nothing to do...

It makes sense to bubble up the `psycopg2.IntegrityError` (as well as the subcase `ConcurrencyError`) so that the retry mechanism can handle this exception. In fact, this exception can be triggered without necessarily a problem with the "logic/business code". This ensures consistent behavior between the business logic and the code executed in `safe_eval`. Task-6215886

Before this commit, subheaders of numeric columns were centered, while the figures in the columns were aligned to the end. This commit ensures that both the subheader and the figures are aligned the same way (center or end). task-6197223