tigrbl-ops-oltp

Transactional OLTP operation handlers for Tigrbl CRUD, bulk, REST, JSON-RPC, and database-backed workloads.

What is tigrbl-ops-oltp?

Transactional OLTP operation handlers for Tigrbl CRUD, bulk, REST, JSON-RPC, and database-backed workloads.

Why use tigrbl-ops-oltp?

Use it when you need this operation-family boundary directly instead of consuming operations through the top-level facade.

When should I install tigrbl-ops-oltp?

Install it for framework internals, extension packages, or focused tests that target this operation plane.

Who is tigrbl-ops-oltp for?

Framework maintainers and extension authors working near Tigrbl operation dispatch.

Where does tigrbl-ops-oltp fit?

tigrbl-ops-oltp lives at pkgs/core/tigrbl_ops_oltp and serves focused operation dispatch behavior inside the Tigrbl runtime model.

How does tigrbl-ops-oltp work?

It contributes operation handlers and dispatch-facing primitives consumed by the facade, runtime, and kernel layers.

Certification Status

• Package status: governed package in the tigrbl/tigrbl workspace.
• Governance source: SSOT registry.
• Release evidence: publish workflow validates package builds, tests, GitHub release assets, and PyPI publication for managed packages.
• Local certification guard: pkgs/core/tigrbl_tests/tests/unit/test_package_badges_and_notices.py verifies every package README keeps the Discord badge, Apache 2.0 badge, explicit Python-version badge, LICENSE, and NOTICE.
• Scope note: this README documents the package boundary. Runtime feature support remains governed by .ssot/ entities and the conformance docs linked below.

Install

uv add tigrbl-ops-oltp

pip install tigrbl-ops-oltp

Surface Coverage

What It Owns

tigrbl-ops-oltp owns the operation-family package boundary. It should be installed when you need this package's focused responsibility without assuming every other Tigrbl workspace package is present.

Implementation orientation:

• tigrbl_ops_oltp: crud/

Public API and Import Surface

• Import roots: tigrbl_ops_oltp.
• Public symbols: Body, Header, Param, Path, Query, bulk_create, bulk_delete, bulk_merge, bulk_replace, bulk_update, clear, count.
• Workspace dependencies: tigrbl-orm, tigrbl-base, tigrbl-core.
• External runtime dependencies: none declared.

Usage Examples

Verify the installed package

python -m pip show tigrbl-ops-oltp
python - <<'PY'
from importlib.metadata import version
print(version("tigrbl-ops-oltp"))
PY

Import the package boundary

import importlib

module = importlib.import_module("tigrbl_ops_oltp")
print(module.__name__)

Import a public symbol

from tigrbl_ops_oltp import Body

print(Body)

Use with the facade when building applications

uv add tigrbl tigrbl-ops-oltp
python - <<'PY'
import tigrbl
print(tigrbl.__name__)
PY

How To Choose This Package

Choose tigrbl-ops-oltp when the quick-answer table matches your use case. Choose tigrbl instead when you want the full public facade. Choose a lower-level package such as tigrbl-core, tigrbl-base, or tigrbl-runtime when you are building framework extensions or testing a specific internal boundary.

Related Packages

• tigrbl-orm
• tigrbl-base
• tigrbl-core
• tigrbl
• tigrbl-runtime

Documentation Links

• Workspace docs
• Package catalog
• Package layout
• Current target
• Current state
• SSOT registry
• Release workflow

Support

• Community: Discord.
• Issues: GitHub Issues.
• Repository: pkgs/core/tigrbl_ops_oltp.

Package-local Boundary

This README is the package-local distribution entry point for tigrbl-ops-oltp. It answers install, usage, API, ownership, and certification-orientation questions for this package. Broader architectural decisions, release status, and cross-package proof chains remain in the repository-level docs and SSOT registry.

License

Licensed under the Apache License, Version 2.0. See LICENSE, NOTICE, and the official Apache 2.0 license text.