Skip to main content

interloper-sql

SQL for interloper: ibis_view, portable views authored as Ibis expressions, and behind the postgres extra a SQL database destination, SQLDestination, a DatabaseDestination over SQLAlchemy Core with the SQLConnection that holds the database URL.

The base package depends on Ibis only, so a package that defines ibis_views pulls in no database driver. interloper-sql[postgres] adds SQLAlchemy and psycopg[binary]; the destination and its connection exist only with it.

One backend serves every SQLAlchemy dialect whose driver is installed. PostgreSQL works with the extra; MySQL, SQLite, Redshift, SQL Server and the rest need their own driver on top.

Setup

The connection is a single SQLAlchemy URL:

Database URL Driver to install
PostgreSQL postgresql+psycopg://user:password@host:5432/db interloper-sql[postgres]
MySQL / MariaDB mysql+pymysql://user:password@host:3306/db pymysql
SQL Server mssql+pyodbc://user:password@host/db?driver=ODBC+Driver+18+for+SQL+Server pyodbc (and the ODBC driver)
Redshift redshift+redshift_connector://user:password@host:5439/db sqlalchemy-redshift, redshift_connector
SQLite sqlite:///path/to/file.db none, in the standard library

Install the driver next to interloper (uv pip install pymysql, or a custom image built from the slim variant). Special characters in the password must be URL-encoded.

The URL carries the password, so it is a secret field: encrypted at rest in a deployed instance and masked in the UI. It also loads from the environment (SQL_URL), so SQLConnection() works with no arguments.

The connection's check runs SELECT 1.

Usage

import interloper as il
from interloper_sql import SQLConnection, SQLDestination

warehouse = SQLDestination(
    connection=SQLConnection(url="postgresql+psycopg://user:password@host:5432/analytics"),
    default_dataset="marketing",
)

In a deployed instance you configure this through the UI instead: add a SQL database connection, then a SQL database destination using it.

Datasets are schemas

An asset's dataset is the SQL schema its table lives in. Without one, the destination's default_dataset applies; without either, the table goes in the connection's default schema (public on PostgreSQL, the database itself on MySQL). A named schema is created on first write when the database supports schemas and it does not exist yet.

Tables

A table is created on first write from the asset's effective schema (declared, or inferred during conform): integers are BIGINT, floats DOUBLE, decimals NUMERIC(38, 9), datetimes timezone-aware timestamps, strings TEXT, and nested or repeated fields JSON. An existing table is never altered: columns it lacks are dropped from the write with a warning, and NaN or infinite floats are written as NULL.

Partitions

Writes replace, inside one transaction:

  • unpartitioned: every row is deleted, then the data inserted;
  • a time partition: the rows inside its half-open bounds (column >= start AND column < end) are deleted, then the data inserted;
  • any other partition: the rows equal to its id are deleted;
  • a window: each partition's rows are deleted, then the whole batch is inserted once.

A failed insert rolls the delete back, so a partition is never left empty. Inserts go in batches of 1000 rows. Reads return rows as list[dict]; reading a table that was never written raises DataNotFoundError.

Metadata

Release files for interloper-sql 0.131.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 interloper-sql 0.131.0
File Size Uploaded Provenance Actions
interloper_sql-0.131.0.tar.gz 12.6 kB Without provenance Details for interloper_sql-0.131.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for interloper-sql 0.131.0
File Interpreter ABI Platform Actions
interloper_sql-0.131.0-py3-none-any.whl Python 3 none any Details for interloper_sql-0.131.0-py3-none-any.whl

Total release size: 28.3 kB

Release files / interloper_sql-0.131.0.tar.gz

Download URL interloper_sql-0.131.0.tar.gz
Size 12.6 kB
Tags Source
SHA-256 checksum
How to use checksums
bcb172db3c400a7a9d2583798929957f429e22fc6f049ade855c9d076aef78f2
BLAKE2b-256 checksum
How to use checksums
54bc58369294fbe1b4fc140a6fb5352da068658ededc70d53b14fbe4b7decd88
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / interloper_sql-0.131.0-py3-none-any.whl

Download URL interloper_sql-0.131.0-py3-none-any.whl
Size 15.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
56253eba2cd2d375f31245e9548b69af00c16bec3abc83f2308cc1e13be9d764
BLAKE2b-256 checksum
How to use checksums
3e36122d8ea7edbbd165dc839d070760c93a5f0b11fe34a8f97428abb6079a80
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for interloper-sql 0.131.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.131.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