YDB Python DBAPI
Introduction
Python DBAPI to YDB, which provides both sync and async drivers and complies with PEP249.
Installation
pip install ydb-dbapi
Usage
To establish a new DBAPI connection you should provide host, port and database:
import ydb_dbapi
connection = ydb_dbapi.connect(
host="localhost", port="2136", database="/local"
) # sync connection
async_connection = await ydb_dbapi.async_connect(
host="localhost", port="2136", database="/local"
) # async connection
For TLS connections, pass PEM certificate contents as bytes through
root_certificates, or use root_certificates_path to load them from a file.
Shared session pools must match the connection API: ydb.QuerySessionPool
for connect() and ydb.aio.QuerySessionPool for async_connect().
Usage of connection:
with connection.cursor() as cursor:
cursor.execute("SELECT id, val FROM table")
row = cursor.fetchone()
rows = cursor.fetchmany(size=5)
rows = cursor.fetchall()
Usage of async connection:
async with async_connection.cursor() as cursor:
await cursor.execute("SELECT id, val FROM table")
row = await cursor.fetchone()
rows = await cursor.fetchmany(size=5)
rows = await cursor.fetchall()
Query parameters
Standard mode (pyformat=True)
Pass pyformat=True to connect() to enable familiar Python DB-API
parameter syntax such as %(name)s and %s. This mode is opt-in: the
default connection mode (pyformat=False) uses YDB-style $name
placeholders instead, so %(name)s and %s do not work unless
pyformat=True is set explicitly. The driver will convert placeholders
and infer YDB types from Python values automatically.
Named parameters — %(name)s with a dict:
connection = ydb_dbapi.connect(
host="localhost", port="2136", database="/local",
pyformat=True,
)
with connection.cursor() as cursor:
cursor.execute(
"SELECT * FROM users WHERE id = %(id)s AND active = %(active)s",
{"id": 42, "active": True},
)
Positional parameters — %s with a list or tuple:
with connection.cursor() as cursor:
cursor.execute(
"INSERT INTO users (id, name, score) VALUES (%s, %s, %s)",
[1, "Alice", 9.8],
)
Use %% to insert a literal % character in the query.
The driver validates pyformat placeholders before executing the query:
- do not mix named
%(name)sand positional%splaceholders in one query; - named placeholders require a
dictwith bare keys like{"id": 1}; - positional placeholders require a
listortuple; - missing or extra parameters raise
ProgrammingError; - keys starting with
$are not allowed inpyformat=Truemode.
Automatic type mapping:
| Python type | YDB type |
|---|---|
bool |
Bool |
int |
Int64 |
float |
Double |
str |
Utf8 |
bytes |
String |
datetime.datetime |
Timestamp |
datetime.date |
Date |
datetime.timedelta |
Interval |
decimal.Decimal |
Decimal(22, 9) |
None |
NULL (passed as-is) |
Explicit types with ydb.TypedValue:
When automatic inference is not suitable (e.g. you need Int32 instead of
Int64, or Json), wrap the value in ydb.TypedValue — it will be passed
through unchanged:
import ydb
with connection.cursor() as cursor:
cursor.execute(
"INSERT INTO events (id, payload) VALUES (%(id)s, %(payload)s)",
{
"id": ydb.TypedValue(99, ydb.PrimitiveType.Int32),
"payload": ydb.TypedValue('{"key": "value"}', ydb.PrimitiveType.Json),
},
)
If the driver cannot infer a YDB type for a Python value, it raises
TypeError. Use ydb.TypedValue for such values or when you need an explicit
YDB type.
Native YDB mode (default, deprecated)
Deprecated. Native YDB mode is the current default for backwards compatibility, but it will be removed in a future release. Migrate to
pyformat=Trueat your earliest convenience.
By default (pyformat=False) the driver passes the query and parameters
directly to the YDB SDK without any transformation.
Passing a list or tuple in native mode raises ProgrammingError.
Use pyformat=True with execute() for positional parameters.
Use $name placeholders in the query and supply a dict with
$-prefixed keys:
connection = ydb_dbapi.connect(
host="localhost", port="2136", database="/local",
)
with connection.cursor() as cursor:
cursor.execute(
"SELECT * FROM users WHERE id = $id",
{"$id": ydb.TypedValue(42, ydb.PrimitiveType.Int64)},
)
Metadata
Release files for ydb-dbapi 0.1.24
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 |
|---|---|---|---|---|
| ydb_dbapi-0.1.24.tar.gz | 21.0 kB | With provenance | Details for ydb_dbapi-0.1.24.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ydb_dbapi-0.1.24-py3-none-any.whl | Python 3 | none | any | Details for ydb_dbapi-0.1.24-py3-none-any.whl |
Total release size: 42.3 kB
Release files / ydb_dbapi-0.1.24.tar.gz
| Download URL | ydb_dbapi-0.1.24.tar.gz |
|---|---|
| Size | 21.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2fdc6a736f023445ebdc466107666c68c52374d7d125e8ba787ff96255ef7991
|
|
BLAKE2b-256 checksum How to use checksums |
f2c703dddc4b71ee572a41147d29e70166bc843a08e68cb34d2876e9838b15bd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 26, 2026.
Transparency logRelease files / ydb_dbapi-0.1.24-py3-none-any.whl
| Download URL | ydb_dbapi-0.1.24-py3-none-any.whl |
|---|---|
| Size | 21.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
65651ea7e060597c64dfc79ff2199383d70e9332e08a3d2149f8e301c0dd2238
|
|
BLAKE2b-256 checksum How to use checksums |
745b30161a715310f4c9ab351ae3fdf769836e083ba6dd9ec6b513537189bc16
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 26, 2026.
Transparency logSecurity for ydb-dbapi 0.1.24
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for ydb_dbapi-0.1.24.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 26, 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.