Skip to main content

Import data from SQL and ODBC data sources.

Project description

License: AGPL-3

Import data from SQL and ODBC data sources.

This module allows import data directly from other databases.

Usage

Go to: Administration module, menu Configuration -> Import from SQL.

Features:
  • Fetched data from the databases are used to build lines equivalent to regular import files. These are imported using the standard “import_data()” ORM method, benefiting from all its features, including xml_ids.

  • Each table import is defined by an SQL statement, used to build the equivalent for an import file. Each column’s name should match the column names you would use in an import file. The first column must provide an unique identifier for the record, and will be used to build its xml_id.

  • SQL columns named “none” are ignored. This can be used for the first column of the SQL, so that it’s used to build the XML Id but it’s not imported to any OpenERP field.

  • The last sync date is the last successfull execution can be used in the SQL using “%(sync)s”, or “:sync” in the case of Oracle.

  • When errors are found, only the record with the error fails import. The other correct records are commited. However, the “last sync date” will only be automaticaly updated when no errors are found.

  • The import execution can be scheduled to run automatically.

Examples:
  • Importing suppliers to res.partner:
    SELECT distinct[SUPPLIER_CODE] as "ref",
        [SUPPLIER_NAME] as "name",
        1 as "is_supplier",
        [INFO] as "comment"
    FROM T_SUPPLIERS
    WHERE INACTIVE_DATE IS NULL and DATE_CHANGED >= %(sync)s'
  • Importing products to product.product:
    SELECT
        PRODUCT_CODE as "ref",
        PRODUCT_NAME as "name",
        'res_partner_id_' + SUPPLIER_ID as "partner_id/id"
    FROM T_PRODUCTS
    WHERE DATE_CHANGED >= %(sync)s'

Known issues / Roadmap

Improvements ideas waiting for a contributor:
  • Allow to import many2one fields (currently not supported). Done by adding a second SQL sentence to get child record list?

  • Allow “import sets” that can be executed at different time intervals using different scheduler jobs.

  • Allow to inactivate/delete OpenERP records when not present in an SQL result set.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback here.

Credits

Contributors

Maintainer

Odoo Community Association

This module is maintained by the OCA.

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

To contribute to this module, please visit http://odoo-community.org.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

File details

Details for the file odoo8_addon_import_odbc-8.0.0.1.3-py2-none-any.whl.

File metadata

File hashes

Hashes for odoo8_addon_import_odbc-8.0.0.1.3-py2-none-any.whl
Algorithm Hash digest
SHA256 c09d0a7cb3d6426e9251ae93566a56690cb2e64ab31cf7ddf5f3bed296376cb3
MD5 aa34999ee4c2077f206c0e739474faaf
BLAKE2b-256 63028b7bd57798442612a7216e255ac70ce7d81aed8c8d318c74e2c03e6edc6d

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page