From 1588837195f057e85ca884bea019e39298bc4765 Mon Sep 17 00:00:00 2001
From: OCA-git-bot
Date: Wed, 4 Dec 2024 13:26:44 +0000
Subject: [PATCH] [BOT] post-merge updates
---
README.md | 1 +
bi_sql_editor/README.rst | 108 ++++++++++----------
bi_sql_editor/static/description/index.html | 30 +++---
setup/_metapackage/pyproject.toml | 3 +-
4 files changed, 72 insertions(+), 70 deletions(-)
diff --git a/README.md b/README.md
index 1dee254c0..585c90eb8 100644
--- a/README.md
+++ b/README.md
@@ -21,6 +21,7 @@ Available addons
----------------
addon | version | maintainers | summary
--- | --- | --- | ---
+[bi_sql_editor](bi_sql_editor/) | 18.0.1.0.0 | [](https://github.com/legalsylvain) | BI Views builder, based on Materialized or Normal SQL Views
[report_xlsx](report_xlsx/) | 18.0.1.0.0 | | Base module to create xlsx report
[sql_request_abstract](sql_request_abstract/) | 18.0.1.0.0 | [](https://github.com/legalsylvain) | Abstract Model to manage SQL Requests
diff --git a/bi_sql_editor/README.rst b/bi_sql_editor/README.rst
index c4e575dd0..7a9b5dd81 100644
--- a/bi_sql_editor/README.rst
+++ b/bi_sql_editor/README.rst
@@ -7,7 +7,7 @@ BI SQL Editor
!! This file is generated by oca-gen-addon-readme !!
!! changes will be overwritten. !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
- !! source digest: sha256:1acb226c184032febd7db6e48ee618c7e5a6899c4685aa78b5b2e7578ebd9ce9
+ !! source digest: sha256:a308e7ec853f7c008503fa6b869b2c088ff431cdd066d5e27a7ec84895b58d4b
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
.. |badge1| image:: https://img.shields.io/badge/maturity-Beta-yellow.png
@@ -61,17 +61,17 @@ Use Cases
this module is interesting for the following use cases
-- You want to realize technical SQL requests, that Odoo framework
- doesn't allow (For exemple, UNION with many SELECT) A typical use
- case is if you want to have Sale Orders and PoS Orders datas in a
- same table
-- You want to customize an Odoo report, removing some useless fields
- and adding some custom ones. In that case, you can simply select the
- fields of the original report (sale.report model for exemple), and
- add your custom fields
-- You have a lot of data, and classical SQL Views have very bad
- performance. In that case, MATERIALIZED VIEW will be a good solution
- to reduce display duration
+- You want to realize technical SQL requests, that Odoo framework
+ doesn't allow (For exemple, UNION with many SELECT) A typical use case
+ is if you want to have Sale Orders and PoS Orders datas in a same
+ table
+- You want to customize an Odoo report, removing some useless fields and
+ adding some custom ones. In that case, you can simply select the
+ fields of the original report (sale.report model for exemple), and add
+ your custom fields
+- You have a lot of data, and classical SQL Views have very bad
+ performance. In that case, MATERIALIZED VIEW will be a good solution
+ to reduce display duration
**Table of contents**
@@ -81,15 +81,15 @@ this module is interesting for the following use cases
Configuration
=============
-- Go to Dashboard / Configuration / SQL Views
+- Go to Dashboard / Configuration / SQL Views
-- tip your SQL request
+- tip your SQL request
- |image1|
+ |image1|
-- Select the group(s) that could have access to the view
+- Select the group(s) that could have access to the view
- |image2|
+ |image2|
Optionnaly, you can add a domain.
@@ -97,34 +97,34 @@ A tipical domain in a multi company context is to write
``['|', ('company_id', '=', False), ('company_id', 'in', company_ids)]``
to make reporting depending on the current companies of the user.
-- Click on the button 'Validate SQL Expression'
+- Click on the button 'Validate SQL Expression'
-- Once the sql request checked, the module analyses the column of the
- view, and propose field mapping. For each field, you can decide to
- create an index and set if it will be displayed on the pivot graph as
- a column, a row or a measure.
+- Once the sql request checked, the module analyses the column of the
+ view, and propose field mapping. For each field, you can decide to
+ create an index and set if it will be displayed on the pivot graph as
+ a column, a row or a measure.
- |image3|
+ |image3|
-- Click on the button 'Create SQL elements'. (this step could take a
- while, if view is materialized)
+- Click on the button 'Create SQL elements'. (this step could take a
+ while, if view is materialized)
-- If it's a MATERIALIZED view:
+- If it's a MATERIALIZED view:
- - a cron task is created to refresh the view. You can so define
- the frequency of the refresh.
- - the size of view (and the indexes is displayed)
+ - a cron task is created to refresh the view. You can so define the
+ frequency of the refresh.
+ - the size of view (and the indexes is displayed)
- |image4|
+ |image4|
-- Before applying the final step, you will need to add a specific
- Parent Menu to use when creating the UI Menu for the report. By
- default, it will be set with the ``SQL Views`` menu, which can be
- changed before creating the UI elements in order to have the report
- accessible from a different place within Odoo.
+- Before applying the final step, you will need to add a specific Parent
+ Menu to use when creating the UI Menu for the report. By default, it
+ will be set with the ``SQL Views`` menu, which can be changed before
+ creating the UI elements in order to have the report accessible from a
+ different place within Odoo.
-- Finally, click on 'Create UI', to create new menu, action, graph view
- and search view.
+- Finally, click on 'Create UI', to create new menu, action, graph view
+ and search view.
.. |image1| image:: https://raw.githubusercontent.com/OCA/reporting-engine/18.0/bi_sql_editor/static/description/01_sql_request.png
.. |image2| image:: https://raw.githubusercontent.com/OCA/reporting-engine/18.0/bi_sql_editor/static/description/02_security_access.png
@@ -143,7 +143,7 @@ To use this module, you need to:
|usage-image1|
-- You can switch to 'Graph' or 'tree' views as any report.
+- You can switch to 'Graph' or 'tree' views as any report.
.. |usage-image1| image:: https://raw.githubusercontent.com/OCA/reporting-engine/18.0/bi_sql_editor/static/description/05_reporting_pivot.png
@@ -168,28 +168,28 @@ Authors
Contributors
------------
-- Sylvain LE GAL (https://twitter.com/legalsylvain)
+- Sylvain LE GAL (https://twitter.com/legalsylvain)
-- Richard deMeester, WilldooIT (http://www.willdooit.com/)
+- Richard deMeester, WilldooIT (http://www.willdooit.com/)
-- David James, WilldooIT (http://www.willdooit.com/)
+- David James, WilldooIT (http://www.willdooit.com/)
-- Guillem Casassas guillem.casassas@forgeflow.com
+- Guillem Casassas guillem.casassas@forgeflow.com
-- Thien Vo thienvh@trobz.com
+- Thien Vo thienvh@trobz.com
-- This module is highly inspired by the work of
+- This module is highly inspired by the work of
- - Onestein: (http://www.onestein.nl/) Module:
- OCA/server-tools/bi_view_editor. Link:
- https://github.com/OCA/reporting-engine/tree/9.0/bi_view_editor
- - Anybox: (https://anybox.fr/) Module :
- OCA/server-tools/materialized_sql_view link:
- https://github.com/OCA/server-tools/pull/110
- - GRAP, Groupement Régional Alimentaire de Proximité:
- (http://www.grap.coop/) Module:
- grap/odoo-addons-misc/pos_sale_reporting link:
- https://github.com/grap/odoo-addons-misc/tree/7.0/pos_sale_reporting
+ - Onestein: (http://www.onestein.nl/) Module:
+ OCA/server-tools/bi_view_editor. Link:
+ https://github.com/OCA/reporting-engine/tree/9.0/bi_view_editor
+ - Anybox: (https://anybox.fr/) Module :
+ OCA/server-tools/materialized_sql_view link:
+ https://github.com/OCA/server-tools/pull/110
+ - GRAP, Groupement Régional Alimentaire de Proximité:
+ (http://www.grap.coop/) Module:
+ grap/odoo-addons-misc/pos_sale_reporting link:
+ https://github.com/grap/odoo-addons-misc/tree/7.0/pos_sale_reporting
Other credits
-------------
diff --git a/bi_sql_editor/static/description/index.html b/bi_sql_editor/static/description/index.html
index f5b63b420..75c8afa35 100644
--- a/bi_sql_editor/static/description/index.html
+++ b/bi_sql_editor/static/description/index.html
@@ -367,7 +367,7 @@ ul.auto-toc {
!! This file is generated by oca-gen-addon-readme !!
!! changes will be overwritten. !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-!! source digest: sha256:1acb226c184032febd7db6e48ee618c7e5a6899c4685aa78b5b2e7578ebd9ce9
+!! source digest: sha256:a308e7ec853f7c008503fa6b869b2c088ff431cdd066d5e27a7ec84895b58d4b
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->

This module extends the functionality of reporting, to support creation
@@ -396,13 +396,13 @@ on a production environment.
this module is interesting for the following use cases
- You want to realize technical SQL requests, that Odoo framework
-doesn’t allow (For exemple, UNION with many SELECT) A typical use
-case is if you want to have Sale Orders and PoS Orders datas in a
-same table
-- You want to customize an Odoo report, removing some useless fields
-and adding some custom ones. In that case, you can simply select the
-fields of the original report (sale.report model for exemple), and
-add your custom fields
+doesn’t allow (For exemple, UNION with many SELECT) A typical use case
+is if you want to have Sale Orders and PoS Orders datas in a same
+table
+- You want to customize an Odoo report, removing some useless fields and
+adding some custom ones. In that case, you can simply select the
+fields of the original report (sale.report model for exemple), and add
+your custom fields
- You have a lot of data, and classical SQL Views have very bad
performance. In that case, MATERIALIZED VIEW will be a good solution
to reduce display duration
@@ -447,18 +447,18 @@ while, if view is materialized)
If it’s a MATERIALIZED view:
-- a cron task is created to refresh the view. You can so define
-the frequency of the refresh.
+- a cron task is created to refresh the view. You can so define the
+frequency of the refresh.
- the size of view (and the indexes is displayed)

-Before applying the final step, you will need to add a specific
-Parent Menu to use when creating the UI Menu for the report. By
-default, it will be set with the SQL Views menu, which can be
-changed before creating the UI elements in order to have the report
-accessible from a different place within Odoo.
+Before applying the final step, you will need to add a specific Parent
+Menu to use when creating the UI Menu for the report. By default, it
+will be set with the SQL Views menu, which can be changed before
+creating the UI elements in order to have the report accessible from a
+different place within Odoo.
Finally, click on ‘Create UI’, to create new menu, action, graph view
and search view.
diff --git a/setup/_metapackage/pyproject.toml b/setup/_metapackage/pyproject.toml
index 398ab3a16..a9d741eae 100644
--- a/setup/_metapackage/pyproject.toml
+++ b/setup/_metapackage/pyproject.toml
@@ -1,7 +1,8 @@
[project]
name = "odoo-addons-oca-reporting-engine"
-version = "18.0.20241112.0"
+version = "18.0.20241204.0"
dependencies = [
+ "odoo-addon-bi_sql_editor==18.0.*",
"odoo-addon-report_xlsx==18.0.*",
"odoo-addon-sql_request_abstract==18.0.*",
]