1.2.0

What's Changed

• Query folding, better performance, new functions, bug fixes by @tmijail in #36

  • Added query folding for GerRowCount.
  • Better performance on GetType (still not optimal, refactoring is needed),
  • Fixed bug when doing successive OnTakes,
  • Added search_count function.
  • Added read_group function. Still need to add some docs,
  • Updated docs for search_read,

• docs: update README.md by @eltociear in #31

New Contributors

• @eltociear made their first contribution in #31

Full Changelog: v1.0.0...v1.2.0

1.1.0

Call for testers

This is an experimental release. If you have reports running on v1.0.0, please try this release and let me know in the associated discussion if you experience any issues or if everything works well.

If you are a new user, use the latest stable release instead.

Changes

• Added query folding support for Table.FirstN
• Added query folding support for Table.Skip
• Added query folding support for Table.SelectColumns
• Added query folding support for Table.Sort

Explanation

As the Power Query documentation says,

The goal of query folding is to offload or push as much of the evaluation of a query to a data source that can compute the transformations of your query.

The query folding mechanism accomplishes this goal by translating your M script to a language that can be interpreted and executed by your data source. It then pushes the evaluation to your data source and sends the result of that evaluation to Power Query.

This operation often provides a much faster query execution than extracting all the required data from your data source and running all transforms required in the Power Query engine.

1.0.0

⚠️ 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.

0.2.0: Odoo 16 compatibility

Changes

• Fixes invalid parent field: res.users.parent_id error on Odoo 16 (#17)
• Fixes error when trying to read empty tables (#9)

0.1.0

Initial public release.

Features:

• search_read function
• Tables generated from ir.models
• Automatic schema from field definitions
• Gateway support