dirigent-block-sql
The SQL block family: sql.query reads rows and sql.execute writes them, both against the
database a sql connection names.
The connection kind holds the URL and its credential, and the driver is SQLAlchemy's, so any dialect with an async driver the worker has installed is addressable.
Engines are packages. A backend that needs more than a driver implements SqlEngine and
registers under the dirigent.sql.engines.v1 entry-point group, and the family asks it what a
valid connection to that backend is, where a database written as a relative path lands, what a
parameter becomes, how a check reaches it, and what a session on it is.
dirigent-block-duckdb is the first, and duckdb:///warehouse.duckdb works once it is
installed.
1 maintainer
Metadata
1 maintainer
Release files for dirigent-block-sql 0.27.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dirigent_block_sql-0.27.0.tar.gz | 13.4 kB | With provenance | Details for dirigent_block_sql-0.27.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dirigent_block_sql-0.27.0-py3-none-any.whl | Python 3 | none | any | Details for dirigent_block_sql-0.27.0-py3-none-any.whl |
Total release size: 30.0 kB
Release files / dirigent_block_sql-0.27.0.tar.gz
| Download URL | dirigent_block_sql-0.27.0.tar.gz |
|---|---|
| Size | 13.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a184a5c97a98215473311f9a5897bebeb4cabe32e5cb77a0c55b3b34476096a5
|
|
BLAKE2b-256 checksum How to use checksums |
6b2658be63660919da391d5caa5052d07f1d1673969c3c313d33d81cd052927b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logRelease files / dirigent_block_sql-0.27.0-py3-none-any.whl
| Download URL | dirigent_block_sql-0.27.0-py3-none-any.whl |
|---|---|
| Size | 16.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
43bb7cccf666b2ef95fbc4110dae6c16a0b666cd0cdc6569f0782a4f9a41d617
|
|
BLAKE2b-256 checksum How to use checksums |
5e16bd1b574ba9b41cfd8cc66e7e296913ffb1551d88cea2d3f3f37da4e0da3b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logSecurity for dirigent-block-sql 0.27.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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for dirigent_block_sql-0.27.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logA 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.
