ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #ecto
Learn how to use Ecto Changesets to prevent mass-assignment vulnerabilities by implementing strict data casting and separating application validation from database constraints.
Learn how Ecto Changesets prevent data corruption by decoupling input casting and validation from database persistence in Elixir.
Ecto.Multi lets you chain inserts, updates, and custom callbacks into a single all‑or‑nothing transaction. This guide shows a concrete example, explains how it works, and lists common pitfalls and verification steps.
Learn how Ecto.Multi lets you compose multiple database operations into an atomic transaction, handle errors cleanly, and avoid common side‑effect pitfalls in Elixir apps.
In a Phoenix project the config/dev.exs file uses config :my_app, MyApp.Repo, url: \"postgres://localhost/my_app_dev\" and the app runs fine locally. In production I switch to a release and change the config to config :my_app, MyApp.Repo, url: System.get_env(\"DATABASE_URL\") . The release starts but the database connection fails, even though DATABASE_URL is
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
elixir