Accounting Sequence - Latam Documents
l10n_latam_account_sequence · odoo/odoo
Merged into l10n_latam_invoice_document in 17.0
Health
35/100
poor
-
Security25/25No findings
-
Activity0/25Last human commit 44 months ago
-
Required by5/250 modules depend on it
-
Maturity5/25In 1 Odoo series since 16.0
Heuristic over the facts below, not an audit · How it's computed
Required by
0
Modules depending on it
External deps
0 pip · 0 bin
Python packages / system binaries
License
LGPL-3
No conflicts with its dependencies
Folder size
0.0 MB
Module directory on disk
Code analysis
2 migration notes
1 model
0 views
0 HTTP endpoints
Migration considerations
AccountMove— Migrating to 19.0: `_sql_constraints` is ignored and its constraints are silently not created: declare `models.Constraint` attributes instead. migration-sql-constraints · source- Raw `cr.execute()` INSERT/UPDATE/DELETE bypasses the ORM (no compute/constrains/tracking/mail): `UPDATE account_move SET name = SUBSTRING(account_move.name, 1, strpos(account_move.name::varchar, ' ('::varchar) -1 ) WHERE l10n_latam_document_type_id IS NOT NULL AND account_move.name LIKE '% (%)' AND move_type IN ('in_invoice', 'in_refund', 'in_receipt');` - re-check the table/column names still match after upgrading. (2 occurrences in this file) migration-raw-sql-write · source
Migration review checklist, not a compatibility verdict. "Migrating to X.0" applies once you upgrade to that version; "Since X.0" means this version already ignores or rejects that code. Methodology
Description
Change the way sequence.mixin works to reduce concurrency errors
Dependencies
Code analysis
Extracted from the source by best-effort static analysis (no code is executed); details may be incomplete.
Views touched 0
No views found for this module.
HTTP endpoints 0
No HTTP endpoints found for this module.
Models touched 1
New fields (0)
No new fields.
Public methods (0)No public methods.