transaction-management
>
Works with
--- name: transaction-management description: > license: MIT --- # 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:** ```sql -- 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](references/postgresql-transactions.md) | PostgreSQL Transactions | | [MySQL Transactions](references/mysql-transactions.md) | MySQL Transactions | | [PostgreSQL Isolation Levels](references/postgresql-isolation-levels.md) | PostgreSQL Isolation Levels | | [MySQL Isolation Levels](references/mysql-isolation-levels.md) | MySQL Isolation Levels | | [PostgreSQL Explicit Locking](references/postgresql-explicit-locking.md) | PostgreSQL Explicit Locking | | [MySQL Locking](references/mysql-locking.md) | MySQL Locking | | [Deadlock Prevention](references/deadlock-prevention.md) | **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
More Database skills
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-database-setup
prisma/skills
Guides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, MongoDB, etc.). Use when setting up a new project, changing databases, or troubleshooting connection issues. Triggers on "configure postgres", "connect to mysql", "setup mongodb", "sqlite setup".
prisma-postgres
prisma/skills
Prisma Postgres setup and operations guidance across Console, create-db CLI, Management API, and Management API SDK. Use when creating Prisma Postgres databases, working in Prisma Console, provisioning with create-db/create-pg/create-postgres, or integrating programmatic provisioning with service tokens or OAuth.

