mirror of
https://github.com/OCA/reporting-engine.git
synced 2025-02-16 16:30:38 +02:00
[BOT] post-merge updates
This commit is contained in:
@@ -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
|
||||
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
|
||||
<p><a class="reference external image-reference" href="https://odoo-community.org/page/development-status"><img alt="Beta" src="https://img.shields.io/badge/maturity-Beta-yellow.png" /></a> <a class="reference external image-reference" href="http://www.gnu.org/licenses/agpl-3.0-standalone.html"><img alt="License: AGPL-3" src="https://img.shields.io/badge/licence-AGPL--3-blue.png" /></a> <a class="reference external image-reference" href="https://github.com/OCA/reporting-engine/tree/18.0/bi_sql_editor"><img alt="OCA/reporting-engine" src="https://img.shields.io/badge/github-OCA%2Freporting--engine-lightgray.png?logo=github" /></a> <a class="reference external image-reference" href="https://translation.odoo-community.org/projects/reporting-engine-18-0/reporting-engine-18-0-bi_sql_editor"><img alt="Translate me on Weblate" src="https://img.shields.io/badge/weblate-Translate%20me-F47D42.png" /></a> <a class="reference external image-reference" href="https://runboat.odoo-community.org/builds?repo=OCA/reporting-engine&target_branch=18.0"><img alt="Try me on Runboat" src="https://img.shields.io/badge/runboat-Try%20me-875A7B.png" /></a></p>
|
||||
<p>This module extends the functionality of reporting, to support creation
|
||||
@@ -396,13 +396,13 @@ on a production environment.</p>
|
||||
<p>this module is interesting for the following use cases</p>
|
||||
<ul class="simple">
|
||||
<li>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</li>
|
||||
<li>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</li>
|
||||
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</li>
|
||||
<li>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</li>
|
||||
<li>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</li>
|
||||
@@ -447,18 +447,18 @@ while, if view is materialized)</p>
|
||||
<li><p class="first">If it’s a MATERIALIZED view:</p>
|
||||
<blockquote>
|
||||
<ul class="simple">
|
||||
<li>a cron task is created to refresh the view. You can so define
|
||||
the frequency of the refresh.</li>
|
||||
<li>a cron task is created to refresh the view. You can so define the
|
||||
frequency of the refresh.</li>
|
||||
<li>the size of view (and the indexes is displayed)</li>
|
||||
</ul>
|
||||
</blockquote>
|
||||
<p><img alt="image4" src="https://raw.githubusercontent.com/OCA/reporting-engine/18.0/bi_sql_editor/static/description/04_materialized_view_setting.png" /></p>
|
||||
</li>
|
||||
<li><p class="first">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 <tt class="docutils literal">SQL Views</tt> menu, which can be
|
||||
changed before creating the UI elements in order to have the report
|
||||
accessible from a different place within Odoo.</p>
|
||||
<li><p class="first">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 <tt class="docutils literal">SQL Views</tt> menu, which can be changed before
|
||||
creating the UI elements in order to have the report accessible from a
|
||||
different place within Odoo.</p>
|
||||
</li>
|
||||
<li><p class="first">Finally, click on ‘Create UI’, to create new menu, action, graph view
|
||||
and search view.</p>
|
||||
|
||||
Reference in New Issue
Block a user