Initial commit: OCA Technical packages (595 packages)

This commit is contained in:
Ernad Husremovic 2025-08-29 15:43:03 +02:00
commit 2cc02aac6e
24950 changed files with 2318079 additions and 0 deletions

View file

@ -0,0 +1,17 @@
Sébastien Beau (Akretion) authored the initial prototype.
Stéphane Bidoul (ACSONE) extended it to version 1.0 to support
multi-line records, store data to import as attachments
and let the user control the asynchronous behaviour.
Other contributors include:
* Anthony Muschang (ACSONE)
* David Béal (Akretion)
* Jonathan Nemry (ACSONE)
* Laurent Mignon (ACSONE)
* Dennis Sluijk (Onestein)
* Guewen Baconnier (Camptocamp)
* `Trobz <https://trobz.com>`_:
* Dzung Tran <dungtd@trobz.com>
* Daniel Duque (FactorLibre)

View file

@ -0,0 +1 @@
The migration of this module from 15.0 to 16.0 was financially supported by Camptocamp

View file

@ -0,0 +1,3 @@
This module extends the standard CSV import functionality
to import files in the background using the OCA/queue
framework.

View file

@ -0,0 +1,4 @@
13.0.1.0.0 (2019-12-20)
~~~~~~~~~~~~~~~~~~~~~~~
* [MIGRATION] from 12.0 branched at rev. a7f8031

View file

@ -0,0 +1,4 @@
* There is currently no user interface to control the chunk size,
which is currently 100 by default. Should this proves to be an issue,
it is easy to add an option to extend the import screen.
* Validation cannot be run in the background.

View file

@ -0,0 +1,29 @@
The user is presented with a new checkbox in the import
screen. When selected, the import is delayed in a background
job.
This job in turn splits the CSV file in chunks of minimum
100 lines (or more to align with record boundaries). Each
chunk is then imported in a separate background job.
When an import fails, the job is marked as such and the
user can read the error in the job status. The CSV chunk
being imported is stored as an attachment to the job, making
it easy to download it, fix it and run a new import, possibly
in synchronous mode since the chunks are small.
Any file that can be imported by the standard import mechanism
can also be imported in the background.
This module's scope is limited to making standard imports
asynchronous. It does not attempt to transform the data nor
automate ETL flows.
Other modules may benefit from this infrastructure in the following way
(as illustrated in the test suite):
1. create an instance of `base_import.import` and populate its fields
(`res_model`, `file`, `file_name`),
2. invoke the `do` method with appropriate options
(`header`, `encoding`, `separator`, `quoting`,
`use_queue`, `chunk_size`).