sqlalchemy_db2
A SQLAlchemy dialect for IBM DB2, backed by pydrda (a pure Python DRDA protocol driver).
Usage
Sync:
from sqlalchemy import create_engine
engine = create_engine(
"db2+syn://user:pass@host:50000/database"
)
Async:
from sqlalchemy.ext.asyncio import create_async_engine
engine = create_async_engine(
"db2+asyn://user:pass@host:50000/database"
)
Optional connect parameters may be passed in the query string, e.g. ?use_ssl=true&timeout=10&ssl_client_cert_path=/path/to/cert.pem.
Metadata
Release files for sqlalchemy-db2 0.1.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 |
|---|---|---|---|---|
| sqlalchemy_db2-0.1.0.tar.gz | 20.7 kB | Without provenance | Details for sqlalchemy_db2-0.1.0.tar.gz |
Release files / sqlalchemy_db2-0.1.0.tar.gz
| Download URL | sqlalchemy_db2-0.1.0.tar.gz |
|---|---|
| Size | 20.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dca7beb02452d6c42b2d9d234cf1c1a5c02573fef26bad602210838211754247
|
|
BLAKE2b-256 checksum How to use checksums |
06dd49b569cc7bc2ba0dbcdddd326cb146539ef2651a9de71118f122581e16d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for sqlalchemy-db2 0.1.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.