Owens
Hello all, I’m curious how you all think about cascade deletion. E.g. when one table belongs_to another table and you specify in the migration “on_delete: delete_all”.
From an application design perspective, when is this the right thing vs wrong thing to do? This question may also relate to GDPR but I’m not sure. For example, I’m developing an education platform where users can take courses. The owner of a course may want to delete that course, but then the students who paid to take it would lose their information related to that course if I did cascade deletion for all the information. So it might be better to “archive” that information in some form to satisfy both parties.
What are your thoughts on striking the right balance?
Where Next?
Trending in Discussions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
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
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
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.
Master modern tools, write cleaner code, and tackle real-world challenges.
**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 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
mbuhot
I like to cascade deletes when deleting an Aggregate Root and having it cascade to the closely related entities encapsulated by the aggregate.
Associations between aggregates don’t need cascading deletes, or even necessarily foreign key constraints between them.
The question I ask myself is “could this group of tables be split off into a separate DB/service in future?” If so, then there can’t be cascading deletes or RI enforced if/when that happens, so try not to rely on it too heavily now.