silverdr
I have a parent, which has_many children. Children have a restrict constraint on the DB level: on_delete: :restrict. Thus the error does not come as a surprise. The surprise part is later:
If you would like to stop this constraint violation from raising an
exception and instead add it as an error to your changeset, please
call `foreign_key_constraint/3` on your changeset with the constraint
`:name` as an option.
The changeset has not defined any constraint.
Now, how and where do I call foreign_key_constraint/3 when everything I do is actually Ecto.Repo.delete/2 for which no changeset is needed? I’d still prefer {:error, _something} being returned rather than having an exception risen
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Producing high quality Elixir screencasts since 2017.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #hex
Our Sponsors
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
joey_the_snake
deleteaccepts changesets so you’d need to convert your struct to take advantage of it.Ecto.Changeset.change(struct)is the simplest way.trisolaran
As @joey_the_snake hinted to, you can create a changeset by wrapping the parent struct into one using change/2.
Then you can call no_assoc_constraint/3 on the parent changeset. Now, when you delete, you will get an error in the changeset if there are any children attached to the parent.
silverdr
Right. While I knew I could wrap the struct in a changeset, the
foreign_key_constraint/3suggestion was misleading. Theno_assoc_constraint/3does the trick neatly though. Thank you guys.