opendbs
The official Python client for OpenDBS, a document and SQL database server.
- No dependencies: standard library only, with a kept-alive HTTP connection.
- Clusters: give several URLs and the client moves to another member when one fails, including during a failover election.
- Safe retries: every write carries an
Idempotency-Key, so a retry after a network error is never applied twice.
Requires Python 3.8 or newer and an OpenDBS 1.0 server.
pip install opendbs
Connect
import os
from opendbs import OpenDBS
# With an API key (admin panel → API keys; can be limited to databases and IPs)
client = OpenDBS("http://localhost:4402", api_key=os.environ["OPENDBS_KEY"])
# Or with a user. The client signs in on the first call and again when the session expires.
client = OpenDBS("http://localhost:4402", username="app", password=os.environ["OPENDBS_PASSWORD"])
# A cluster: list the members
client = OpenDBS(["http://10.0.0.5:4402", "http://10.0.0.6:4402", "http://10.0.0.7:4402"], api_key="...")
Options: api_key, username, password, totp (2FA code), token, timeout (seconds, default 30), failover (seconds to keep trying other members, default 20), verify_tls (default True).
A client keeps one connection open and is not thread-safe: create one per thread. It can be used as a context manager (with OpenDBS(...) as client:).
Documents
client.create_database("shop")
shop = client.database("shop")
shop.create_rack("events") # NoSQL rack: any JSON
shop.create_table("customers", { # SQL table: typed columns
"name": {"type": "string", "required": True},
"email": {"type": "string", "required": True, "unique": True},
"age": {"type": "integer"},
})
customers = shop.table("customers")
new_id = customers.insert({"name": "Asha", "email": "asha@example.com", "age": 31})
customers.insert_many([{"name": "Ravi", "email": "ravi@example.com", "age": 45}]) # all or nothing
page = customers.find({"age": {"$gte": 18}}, sort=("age", "desc"), limit=20, skip=0)
print(page["total"], [c["name"] for c in page["results"]])
doc = customers.get(new_id) # None when missing
customers.patch(new_id, {"age": 32}) # merge fields
customers.update(new_id, {"name": "Asha", "email": "asha@example.com", "age": 33}) # replace
customers.delete(new_id)
customers.create_index(["name", "age"]) # compound index
SQL
# ? (or $1) placeholders are never parsed as SQL: use them for any user input.
res = shop.sql(
"SELECT c.name, COUNT(*) AS orders FROM customers c "
"JOIN orders o ON o.customer_id = c.id WHERE o.total > ? GROUP BY c.name",
[20],
)
for row in res["result"]:
print(row["name"], row["orders"])
Aggregation, search, transactions
by_city = shop.rack("events").aggregate([
{"$match": {"type": "purchase"}},
{"$group": {"_id": "$city", "revenue": {"$sum": "$amount"}}},
{"$sort": {"revenue": -1}},
])
shop.rack("products").fuzzy_search("name", "lapptop")
shop.rack("products").vector_search("embedding", [0.12, 0.4, 0.9], k=10)
# Atomic across racks. tx.insert() returns a reference to the new id.
def work(tx):
order = tx.insert("shop", "orders", {"customer_id": "1", "total": 40})
tx.insert("shop", "order_items", {"order_id": order, "sku": "LAMP-1"})
tx.patch("shop", "stock", "7", {"qty": 11})
client.transaction(work)
Errors
Failed requests raise OpenDBSError with status (the HTTP status, or 0 if there was no response) and body (the server's response).
from opendbs import OpenDBSError
try:
customers.insert({"name": "Dup", "email": "asha@example.com"})
except OpenDBSError as e:
if e.status == 400:
print(e)
Upgrading from 1.0.0 / 1.0.1
Code written for the earlier client keeps working. Its methods are still there and return the same values: login(username, password), set_token, register, regenerate_api_key, list_databases(include_racks=), create_database, delete_database, list_racks, create_rack(db, name, type=, schema=), delete_rack, clear_rack, insert(db, rack, doc), find(db, rack, query), find_one(db, rack, id), update, delete, sql(db, query), search, fuzzy_search, vector_search, create_backup and list_backups. The base_url, token and ignore_ssl arguments are accepted too.
Differences:
requestsis no longer a dependency.- Errors are
OpenDBSError(withstatusandbody). It is still anException, soexcept Exceptionkeeps working, but the message no longer starts with "OpenDBS Error:". fuzzy_searchandvector_searchcalled the wrong endpoint in the earlier client. They work now.
License
CC BY-NC 4.0. Non-commercial use is free with attribution.
Metadata
Release files for opendbs 1.0.2
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 | |
|---|---|---|---|---|
| opendbs-1.0.2.tar.gz | 12.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| opendbs-1.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.4 kB
Release files / opendbs-1.0.2.tar.gz
| Download URL | opendbs-1.0.2.tar.gz |
|---|---|
| Size | 12.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1d9dfaa209920214efe007a7a641cdf374af1158b9684750fae88e022ee0c81f
|
|
BLAKE2b-256 checksum How to use checksums |
b76e8dc4957a3227a0ae8064ac374a8f2e225af9d22c414639a1764e6fe01773
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.7
|
Release files / opendbs-1.0.2-py3-none-any.whl
| Download URL | opendbs-1.0.2-py3-none-any.whl |
|---|---|
| Size | 10.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
23039a4ecb0ed7dcf6133cca1908f4cc72a53f7e3d4e3c7b613201a706264dd0
|
|
BLAKE2b-256 checksum How to use checksums |
83c18c806794c1d057595380fa7e023c1641a1317b6cfc81b66c5a31f427c611
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.7
|
Security for opendbs 1.0.2
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.