AT Common Utils
A collection of common utilities for AT backend services.
Package Structure
at_common_util/
├── db/ # Database related utilities
│ ├── __init__.py # Package exports
│ ├── storage.py # Database connection and data access (CRUD operations)
│ └── query.py # Query building utilities
├── workflow/ # Workflow related utilities
│ ├── __init__.py # Package exports
│ ├── core/ # Core workflow components
│ └── utils/ # Workflow utility functions
└── examples/ # Example implementations
└── db/ # Database usage examples
Installation
pip install -e /path/to/at-common-util
Or include in your requirements.txt:
-e /path/to/at-common-util
Database Utilities
The package provides a comprehensive database access layer with three main components:
- Storage - Connection management, session handling, and CRUD operations
- StorageManager - Registry for managing multiple storage instances (e.g., for multiple databases)
- QueryBuilder - Fluent API for constructing complex queries
Basic Usage
from at_common_util.db import Storage, StorageManager
from app.config import settings
# Option 1: Use the Storage class directly
storage = Storage()
storage.init(settings.DB_CONNECTION_URL)
# Option 2: Use the StorageManager for multiple database connections
default_storage = StorageManager.get_storage("default", settings.DB_CONNECTION_URL)
analytics_storage = StorageManager.get_storage("analytics", settings.ANALYTICS_DB_URL)
# Use the storage in your data access layer
async def get_user_by_id(user_id):
from app.models import User
return await default_storage.get_by_field(User, "id", user_id)
async def create_user(user_data):
from app.models import User
user = User(**user_data)
return await default_storage.create(user)
async def update_user(user_id, update_data):
from app.models import User
return await default_storage.update_by_field(User, "id", user_id, update_data)
async def delete_user(user_id):
from app.models import User
return await default_storage.delete_by_field(User, "id", user_id)
Transaction Support
For operations that require transaction support:
from app.models import User, Profile
async def create_user_with_profile(user_data, profile_data):
async with storage.transaction() as session:
# Create user
user = User(**user_data)
session.add(user)
await session.flush() # Flush to get the user ID
# Create profile with user ID reference
profile = Profile(user_id=user.id, **profile_data)
session.add(profile)
# Transaction is automatically committed if no exceptions occur
return user
Query Builder API
For more complex queries, use the QueryBuilder:
from at_common_util.db import QueryBuilder
from sqlalchemy import desc
from app.models import User
async def search_users(criteria):
# Use the query builder to construct a complex query
query = QueryBuilder.for_model(User) \
.filter_by(is_active=True) \
.filter(User.age > 18) \
.order_by(desc(User.created_at)) \
.group_by(User.role) \
.limit(10) \
.offset(20) \
.build()
# Execute the query using storage's session
async with storage.get_session() as session:
result = await session.execute(query)
return result.scalars().all()
Available Storage Methods
query(model_class, filters=None, sort=None, limit=None, offset=None): Query records with optional filtering, sorting, and paginationfind_one(model_class, filters=None): Find a single record matching the filterscreate(model_obj): Create a new recordcreate_many(model_objects): Create multiple records in a transactionupdate_by_field(model_class, field_name, field_value, update_data): Update a record by a field valueget_by_field(model_class, field_name, field_value): Get a record by a field valuedelete_by_field(model_class, field_name, field_value): Delete a record by field valuedelete_many_by_field(model_class, field_name, values): Delete multiple records by field valuescount(model_class, filters=None): Count the number of recordsdispose(): Cleanup database connectionsshutdown(): Close all database connections when shutting down the app
Metadata
Release files for at-common-util 0.1.3
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 |
|---|---|---|---|---|
| at_common_util-0.1.3.tar.gz | 32.5 kB | Without provenance | Details for at_common_util-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| at_common_util-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for at_common_util-0.1.3-py3-none-any.whl |
Total release size: 74.7 kB
Release files / at_common_util-0.1.3.tar.gz
| Download URL | at_common_util-0.1.3.tar.gz |
|---|---|
| Size | 32.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0a112c5a344c9b515659b6736da75abe29025bf2fed0bb11c12189ff6099ff64
|
|
BLAKE2b-256 checksum How to use checksums |
0e665aac85ebdd350970e7c190c61798a3b2b3b4d1f094d26e393cfdda56e9ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Release files / at_common_util-0.1.3-py3-none-any.whl
| Download URL | at_common_util-0.1.3-py3-none-any.whl |
|---|---|
| Size | 42.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
09f61feeae90868659d36cb35c872f099798c49a42bdaf9a58c3abe6f45b028c
|
|
BLAKE2b-256 checksum How to use checksums |
83aad77f7c88757bc5f788208199e80b889274faaff66ac919eac2b5ba30d20d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Security for at-common-util 0.1.3
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.