ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #ecto
Goal Ensure that rolling back a schema migration does not inadvertently lose or corrupt data. Current Constraints Ecto requires a down function for every migration; if omitted the migration is deemed irreversible. The alter table DSL does not automatically generate reverse operations for added columns or renamed fields, and the :force option can silently tru
The goal is to prevent sensitive schema fields from being exposed in API responses without relying on per-endpoint allow lists. Ecto.Schema does not define a built-in private or public field option, and field visibility is not enforced at the schema or repository level. Output shaping is typically delegated to JSON serialization, such as Jason derive with on
Goal: Determine a reliable way to detect and remove a partially created index when a concurrent index migration fails in Ecto 3.0, so that the migration can be retried without leaving orphaned schema objects. Constraints: Because Ecto disables the transaction wrapper for create_index/3 with concurrently: true , a failure does not trigger an automatic rollbac
For a low‑traffic application I want to keep the Ecto repository’s resource usage minimal while still answering requests promptly. The repository creates connection pools that can consume memory and database slots even when idle, and features such as query caching or detailed logging add overhead that may be unnecessary for infrequent workloads. I am conside
Symptom When the IP address associated with a hostname used by an Ecto.Repo changes after the connection pool has been started, existing connections continue to resolve to the former address until the pool is recycled. The underlying behavior stems from Erlang’s :inet resolver being called only when a socket is first opened, and SSL/TLS certificate validatio
An Ecto application connecting to PostgreSQL works in local development but is being deployed behind PgBouncer in transaction pooling mode (as is common with managed Postgres such as RDS Proxy, Supabase, or Cloud SQL). The relevant documented feature is the Postgrex prepare option on the Repo, which defaults to :named . Named prepared statements are bound to