Master Odoo ORM for Efficient Data Operations

Odoo ORM Expert helps turn a requested data operation into idiomatic Odoo ORM code with explanations. It covers reading and writing records, constructing domain filters, working with relational fields and avoiding N+1 queries. You can request a new operation or submit existing code for a performance review.

The supported work includes search(), browse(), create(), write() and unlink(), alongside computed, stored and related fields. Domain filters can target views or server actions. A search example selects confirmed sale orders for one customer within the UTC calendar year, orders them by descending date and limits the result to 50 records.

Use it when implementing model data access, assembling complex domains or improving bulk operations. It encourages search_count() when only a count is needed and the with_context method for passing context without directly changing self.env.context. Avoid search() inside a loop and prefer ORM operations for standard work.

It does not deeply cover cr.execute() raw SQL patterns, partitioning strategies, transient models or wizards. SQL-level optimization belongs with the Odoo performance tuner. Stored computed fields can add substantial write overhead, and SaaS and On-Premise behavior can differ because of configuration overrides.

Mention @odoo-orm-expert and describe the desired operation, model and authorized record scope, or provide code to review. The result is an ORM implementation with explanations and optimization guidance. Computed field fragments illustrate the relationship between storage and dependencies:

total_order_count = fields.Integer(
    string='Total Orders',
    compute='_compute_total_order_count',
    store=True
)

@api.depends('sale_order_ids')
def _compute_total_order_count(self):
    for record in self:
        record.total_order_count = len(record.sale_order_ids)

These fragments require appropriate imports, record definitions and model context. For bulk writes, select explicit approved IDs, discard nonexistent records and write only confirmed values. Missing country data is not evidence that a record belongs in the United States.

The guidance works with Odoo recordsets and model environments. It recommends mapped(), filtered() and sorted() where appropriate, while warning that these operations can load large recordsets. Batch writes reduce repeated calls but can still trigger compute or tracking queries; measure actual query counts rather than assuming one SQL query.

Keep Date values and Datetime values distinct. Python date and datetime objects are supported, but truncating a timestamp or mixing types can change comparisons. Business-year boundaries need UTC bounds derived from the intended business timezone. Use sudo() sparingly because it bypasses access rules, justify its boundary and test record-rule and multi-company isolation.