Odoo Changelog — 2025-08-07

Thursday, August 7, 2025

2 changes · saas-18.3

Improvements(2)

Enhancements to existing features

[IMP] base: allow to ensure RW cursor

Coresaas-18.3base

This change lets the system confirm that a database operation has write access before attempting changes. It helps avoid noisy warnings and tracebacks in read-only situations, improving reliability for internal testing and transaction handling.

Original PR description

Before this commit, when a readonly transaction tried to write data, a
warning would be logged upon raised psycopg2.errors.ReadOnlySqlTransaction
The system would have to try to write before it would retry with a RW
cursor. For some methods used in test, this can be an issue because the
warning will raise a traceback. In this case, we would like a mechanism
to make sure the cursor is RW before it tries and raise the
ReadOnlySqlTransaction error.

taskid-4982555




---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#database#transactions#reliability

[IMP] account_online_synchronization: create initial bank statement

PR #90070

Enterprisesaas-18.3account_online_synchronizationMEDIUM

The first bank account sync now creates a proper opening bank statement instead of a placeholder transaction. This prevents fake accounting entries, improves starting balance accuracy, and makes initial bank reconciliation more reliable.

Original PR description

Before:
- When syncing a bank account for the first time, the system created a dummy
 bank statement line to fill missing statement data.
- This was not linked to a real transaction and could confuse users or lead 
 to inaccurate reporting.

After:
- Replaced the dummy statement line logic with the creation of a proper 
  opening bank statement.
- The system now accurately sets the starting balance and the current 
  balance based on the imported transactions.
- This logic only applies when no previous bank statement lines exist for the 
 journal and the current balance differs from the sum of imported transactions.

Impact:
- Prevents creation of fake bank transactions and journal entries during 
 initial sync, ensuring accurate accounting from the start.
- Improves performance and reliability by calculating the correct
 opening balance using real transaction data and provided bank balance.

TaskID-4815622

#bank synchronization#accounting#opening balance

Before this commit, when a readonly transaction tried to write data, a warning would be logged upon raised psycopg2.errors.ReadOnlySqlTransaction The system would have to try to write before it would retry with a RW cursor. For some methods used in test, this can be an issue because the warning will raise a traceback. In this case, we would like a mechanism to make sure the cursor is RW before it tries and raise the ReadOnlySqlTransaction error. taskid-4982555 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Before: - When syncing a bank account for the first time, the system created a dummy bank statement line to fill missing statement data. - This was not linked to a real transaction and could confuse users or lead to inaccurate reporting. After: - Replaced the dummy statement line logic with the creation of a proper opening bank statement. - The system now accurately sets the starting balance and the current balance based on the imported transactions. - This logic only applies when no previous bank statement lines exist for the journal and the current balance differs from the sum of imported transactions. Impact: - Prevents creation of fake bank transactions and journal entries during initial sync, ensuring accurate accounting from the start. - Improves performance and reliability by calculating the correct opening balance using real transaction data and provided bank balance. TaskID-4815622