# capy-db
SeaORM database connections and explicit migrations for Capy.
Applications normally depend on `capy-framework` as `capy` and use its public facade.
Production Foundation validates maximum/minimum pool sizes and connect, acquire,
and idle timeouts. Startup gets an independent connection deadline. SQLite memory
databases retain one pooled connection. Logs expose only the backend and pool
maximum, and HTTP failures never expose driver details or connection URLs.
`Seeds` runs an application-owned callback in one transaction. The callback receives
`SeedContext` with the transaction and typed configuration. `capy db:seed` is
explicit and refuses environments other than development/test before connecting.
See [seeding](https://github.com/capy-rs/capy/blob/main/docs/seeding.md).
MIT licensed. See LICENSE. This is an initial developer preview, not a production-readiness claim.