dlt.common.libs.ibis

_DltBackend Objects

class _DltBackend(SQLBackend, NoUrl, NoExampleLoader)

View source on GitHub

Ibis backend that delegates execution to dlt's native SQL engine.

To make Ibis expressions executable, they need to be bound to a table on the backend (i.e., data that exists somewhere). By default, Ibis backends work by creating and maintaining a connection to the backend.

This DltBackend is "lazier" and doesn't make a connection to the backend where the data lives ("backend" in Ibis, "destination" in dlt). Instead, it uses dlt metadata to register what table exists and create bound expressions.

For example, if you use Ibis with the Snowflake backend, you will get use Ibis' implementation. If you use the DltBackend with a Snowflake destination, you will use the dlt SQL client for Snowflake. The SQL query created should be the same because dlt internally uses the ibis -> sqlglot compiler, but the actual execution might differ. This is especially likely when calling .execute() or other methods that return data in memory.

from_dataset

@classmethod
def from_dataset(cls, dataset: dlt.Dataset) -> _DltBackend

View source on GitHub

Create an Ibis DltBackend from a dlt.Dataset

This enables dlt.Relation.to_ibis() to create bound tables.

list_tables

def list_tables(
        *,
        like: Optional[str] = None,
        database: Union[tuple[str, str], str, None] = None) -> list[str]

View source on GitHub

Return the list of table names