ecto
/ecto
Design and debug Elixir persistence with Ecto. Use for schemas, changesets, queries, preloads, transactions, migrations, multi-tenancy, and data access through application contexts. Covers database query performance and connection pools.
- Author
- georgeguimaraes ↗
- Repository
- claude-code-elixir ↗
- Licence
- Apache-2.0
- Last repository change
- 19.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 19.09.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Design and debug Elixir persistence with Ecto. Use for schemas, changesets, queries, preloads, transactions, migrations, multi-tenancy, and data access through application contexts. Covers database query performance and connection pools.
Original author description
Design and debug Elixir persistence with Ecto. Use for schemas, changesets, queries, preloads, transactions, migrations, multi-tenancy, and data access through application contexts. Covers database query performance and connection pools.
How it works
- Context = Setting That Changes Meaning
- Cross-Context References: IDs, Not Associations
- DDD Patterns as Pipelines
- Schema ≠ Database Table
- Multiple Changesets per Schema
- Multi-Tenancy: Composite Foreign Keys
- Preload vs Join Trade-offs
- CRUD Contexts Are Fine
- Gotchas from Core Team
- Idioms
SKILL.md preview
---
name: ecto
description: Design and debug Elixir persistence with Ecto. Use for schemas, changesets, queries, preloads, transactions, migrations, multi-tenancy, and data access through application contexts. Covers database query performance and connection pools.
---
# Ecto
Model persistence, compose queries, and keep data access within application boundaries.
## Context = Setting That Changes Meaning
Context isn't just a namespace—it changes what words mean. "Product" means different things in Checkout (SKU, name), Billing (SKU, cost), and Fulfillment (SKU, warehouse). Each bounded context may have its OWN Product schema/table.
**Think top-down:** Subdomain → Context → Entity. Not "What context does Product belong to?" but "What is a Product in this business domain?"
## Cross-Context References: IDs, Not Associations
```elixir
schema "cart_items" do
field :product_id, :integer # Reference by ID
# NOT: belongs_to :product, Catalog.Product
end
```
Query through the context, not across associations. Keeps contexts independent and testable.
## DDD Patterns as Pipelines
```elixir
def create_product(params) do
params
|> Products.build() # Factory: unstructured → domain
|> Products.validate() # Aggregate: enforce invariants
|> Products.insert() # Repository: persist
end
```
Use events (as data structs) to compose bounded contexts with minimal coupling.
## Schema ≠ Database Table
| Use Case | Approach |
|----------|----------|
| Database table | Standard `schema/2` |
| Form validation only | `embedded_schema/1` |
| API request/response | Embedded schema or schemaless |
## Multiple Changesets per Schema
```elixir
def registration_changeset(user, attrs) # Full validation + password
def profile_changeset(user, attrs) # Name, bio only
def admin_changeset(user, attrs) # Role, verified_at
```
Different operations = different changesets.
## Multi-Tenancy: Composite Foreign Keys
```elixir
add :post_id, references(:posts, with: [org_id: :org_id], match: :full)
```
Use `prepare_query/3` for automatic scoping. Raise if `org_id` missing.
## Preload vs Join Trade-offs
| Approach | Best For |
|----------|----------|
| Separate preloads | Has-many with many records (less memory) |
| Join preloads | Belongs-to, has-one (single query) |
Join preloads can use 10x more memory for has-many.
## CRUD Contexts Are Fine
> "If you have a CRUD bounded context, go for it. No need to add complexity."
Use generators for simple cases. Add DDD patterns only when business logic demands it.
## Gotchas from Core Team
### CTE Queries Don't Inherit Schema Prefix
In multi-tenant apps, CTEs don't get the parent query's prefix.
**Fix:** Explicitly set prefix: `%{recursive_query | prefix: "tenant"}`
### Parameterized Queries ≠ Prepared Statements
- **Parameterized queries:** `WHERE id = $1` — always used by Ecto
- **Prepared statements:** Query plan cached by name — can be disabled
**pgbouncer:** Use `prepare: :unnamed` (disables prepared statements, keeps parameterized queries).
### pool_count vs pool_size
More pools with fewer connections = better for benchmarks. **But** with mixed fast/slow queries, a single larger pool gives better latency.
**Rule:** `pool_count` for uniform workloads, larger `pool_size` for real apps.
### Sandbox Mode Doesn't Work With External Processes
Cachex, separate GenServers, or anything outside the test process won't share the sandbox transaction.
**Fix:** Make the external service use the test process, or accept it's not in the same transaction.
### Null Bytes Crash Postgres
PostgreSQL rejects null bytes even though they're valid UTF-8.
**Fix:** Sanitize at boundaries: `String.replace(string, "\x00", "")`
### preload_order for Association Sorting
```elixir
has_many :comments, Comment, preload_order: [desc: :inserted_at]
```
Note: Doesn't work for `through` associations.
### Runtime Migrations Use List API
```elixir
Ecto.Migrator.run(Repo, [{0, Migration1}, {1, Migration2}], :up, opts)
```
## Idioms
- Prefer `Repo.insert/1` over `Repo.insert!/1`—handle `{:ok, _}` / `{:error, _}` explicitly
- Use `Repo.transact/1` (Ecto 3.12+) for simple transactions instead of `Ecto.Multi`
## Red Flags - STOP and Reconsider
- belongs_to pointing to another context's schema
- Single changeset for all operations
- Preloading has-many with join
- CTEs in multi-tenant apps without explicit prefix
- Using pgbouncer without `prepare: :unnamed`
- Testing with Cachex/GenServers assuming sandbox shares transactions
- Accepting user input without null byte sanitization
**Any of these? Re-read the Gotchas section.**
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · georgeguimaraes/claude-code-elixir | 100 | Apache-2.0 |
| vinnie357/claude-skills | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 7c342a97ef62 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100elixir-ecto-patterns
Use when Elixir Ecto patterns including schemas, changesets, queries, and transactions. Use when building database-driven Elixir applications. - 100ecto-patterns
Use when a task touches Ecto, even a how-to question: schemas, changesets, validations, queries, preloads, Multi… - 100estack-ecto
Implement Ecto data access, ownership, changesets, transactions, and safe migrations. Use when editing schemas, queries, tenant-scoped contexts, or database writes. - 100ecto-patterns
Use when a task touches Ecto, even a how-to question: schemas, changesets, validations, queries, preloads, Multi, migrations, constraints, money fields. Load it before writing Ecto code. Skip for Ash. - 100ecto-schemas
Use when defining and working with Ecto schemas including field types, associations, and embedded schemas. Use when modeling database entities in Elixir. - 100phoenix
Use when building an Elixir web app with Phoenix — contexts, Ecto schemas, changesets and migrations, LiveView, channels and PubSub, the generators, and the boundary between domain logic and the web layer. Covers the classic LiveView over-rendering and Ecto N+1 traps. NOT pure…