Skip to content

1.0.0

Latest
Compare
Choose a tag to compare
@tmijail tmijail released this 30 Jun 21:30

⚠️ Warning: Breaking changes ⚠️

This release produces different query results compared to v0.1.0 and v0.2.0. This means that your reports might not work if you created them in v0.1.0 and try to run them in v1.0.0.

Updating a report to work on v1.0.0 is not hard but if you can't do it right away, use v0.2.0 instead.

Changes

  • Queries don't return non store fields unless specified in search_read's fields parameter.

Explanation

Non store fields are fields which are - uh - not stored in Odoo's database. That means that each time you want to read them, Odoo has to run some calculations to figure out what to return. Some of those calculations are fast and some are really slow. It makes sense to avoid querying them unless you really need them.

Also, some non store fields throw errors unless read on a very specific context. For example, there might be an account.move field which works fine when read on an invoice but which throws errors on every other type of account.move. This causes some tables in the Get data dialog to be inaccessible.

If you need to access a non store field, you can do it by using search_read.