SKILL.md
Transaction Management
Table of Contents
- [Overview](#overview)
- [When to Use](#when-to-use)
- [Quick Start](#quick-start)
- [Reference Guides](#reference-guides)
- [Best Practices](#best-practices)
Overview
Implement robust transaction management with ACID compliance, concurrency control, and error handling. Covers isolation levels, locking strategies, and deadlock resolution.
When to Use
- ACID transaction implementation
- Concurrent data modification handling
- Isolation level selection
- Deadlock prevention and resolution
- Transaction timeout configuration
- Distributed transaction coordination
- Financial transaction safety
Quick Start
Simple Transaction:
-- Start transaction
BEGIN;
-- Multiple statements
UPDATE accounts SET balance = balance - 100 WHERE id = 1;
UPDATE accounts SET balance = balance + 100 WHERE id = 2;
-- Commit changes
COMMIT;
-- Or rollback
ROLLBACK;Reference Guides
Detailed implementations in the references/ directory:
| Guide | Contents |
|---|---|
| PostgreSQL Transactions | PostgreSQL Transactions |
| MySQL Transactions | MySQL Transactions |
| PostgreSQL Isolation Levels | PostgreSQL Isolation Levels |
| MySQL Isolation Levels | MySQL Isolation Levels |
| PostgreSQL Explicit Locking | PostgreSQL Explicit Locking |
| MySQL Locking | MySQL Locking |
| Deadlock Prevention | PostgreSQL - Deadlock Detection: |
Best Practices
✅ DO
- Follow established patterns and conventions
- Write clean, maintainable code
- Add appropriate documentation
- Test thoroughly before deploying
❌ DON'T
- Skip testing or validation
- Ignore error handling
- Hard-code configuration values