Skip to main content

Intake-ODBC

Build Status Documentation Status

ODBC Plugin for Intake

Open Database Connectivity (ODBC) provides a standardised interface to many data-base systems and other data sources capable of similar functionality. It passes an SQL text query to the backend via a driver and routes the resultant data back to the calling program.

ODBC can access data in several Data Source Names (DSNs), each of which constitutes a specific connection to a specific database system of a given type.

User Installation

To install the intake-odbc plugin, execute the following command

conda install -c intake intake-odbc

In most cases, the end-users of ODBC data do not configure their own DSNs, merely reference an existing system-wide configuration. Each DSN will be referenced by a unique name, and in general have different requirements in terms of further required parameters. All of this may be defined in the Intake catalog, so that each catalog entry executes a query on some ODBC backend without the user having to know how this is achieved.

In order to set up the ODBC system on a machine, general guidance can be found on the turbodbc pages (this is the library used by this plugin): odbc confguration, database configuration.

Developer Installation

  • Create a development environment with conda create. Then install the dependencies:
conda install -c intake intake turbodbc pandas unixodbc
  • Development installation:
git clone https://github.com/ContinuumIO/intake-odbc
cd intake-odbc
python setup.py develop --no-deps
  • Create a DB to connect to, if you do not have an existing ODBC configuration. The module tests/util.py contains functions to start and stop MS SQL and PostgreSQL docker images that might be useful. You will generally need a driver, appropriate for your system and the DB backend you wish to connect to.

  • Set up odbc config, e.g., the two .ini files provided. The default location of these files is system wide at /usr/local/etc, but you can override this by specifying an environment variable before starting python, e.g.,

    export ODBCSYSINI=/path/to/intake-odbc/examples

Metadata

Release files for intake-odbc 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for intake-odbc 0.2.0
File Size Uploaded Provenance Actions
intake-odbc-0.2.0.tar.gz 26.7 kB Without provenance Details for intake-odbc-0.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for intake-odbc 0.2.0
File Interpreter ABI Platform Actions
intake_odbc-0.2.0-py3-none-any.whl Python 3 none any Details for intake_odbc-0.2.0-py3-none-any.whl

Total release size: 33.0 kB

Release files / intake-odbc-0.2.0.tar.gz

Download URL intake-odbc-0.2.0.tar.gz
Size 26.7 kB
Tags Source
SHA-256 checksum
How to use checksums
696c61ac767676bd46137907f7b57b08619a087d9ace2182f4ca400a88d9f473
BLAKE2b-256 checksum
How to use checksums
f5144c0493e737ddf29554fd7925a73ef7d6023a19266c2eb1ee471d4222f581
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.2 CPython/3.11.3

Release files / intake_odbc-0.2.0-py3-none-any.whl

Download URL intake_odbc-0.2.0-py3-none-any.whl
Size 6.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
91f14c3d86ab070787ffd07287ad991bf94243ced817e41ded1f4cf553376880
BLAKE2b-256 checksum
How to use checksums
94ca443559228ac69d6aa1d63b2e39b0790c77f25959283c9db5d5b6047372bc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.2 CPython/3.11.3

Security for intake-odbc 0.2.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.2.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page