elt547
I really don’t like having “deleted” flags and such on database records. I thought about using elixir processes to schedule a deletion with :timer.sleep, and sending a kill message if the user clicks the undo button. Are there obvious drawbacks to implementing “undoable” actions this way?
# Schedule the deletion
pid = spawn(fn -> :timer.sleep(10_000); Posts.delete(post) end)
# User clicks the undo button
Process.exit(pid, :kill)
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
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
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #elixirconf-us
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #security
- #elixirconf-eu
- #api
- #forms
- #performance
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
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.
Master modern tools, write cleaner code, and tackle real-world challenges.
The deployment platform built for Elixir: PaaS ease, VPS control.
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)
al2o3cr
Two things jump out at first glance:
elt547
Yeah actually I’m thinking, especially because of the nature of the application, it might be better to change the logic to something more similar to “hide from feed” or “archive.”
As a side-note, is there some way to prevent the second case from happening without persisting the actions to disk somehow?
benwilson512
Not really no.
More to the point though, I’m not sure that the code here does what you want it to do. It won’t delete the records until 10 seconds in the future at all, which means if your user loads the page in another tab, the records will still show as not deleted.
A more traditional way to do this is to have a
deleted_atcolumn that you set immediately toNOW()when the user clicks delete. If you want to actually remove the rows at a future point you can clean it up later.