rubysherpas/paranoia
View on GitHub ↗ ★ 2,914 Ruby
acts_as_paranoid for Rails 5, 6 and 7
5 mentions on Hacker News by 5 people: 0 stories, 5 comments · first 2016-08-30 · latest 2022-07-20
20082026
-
…to using Rails features. And everything works together nicely assuming you do things the Rails way. https://github.com/rubysherpas/paranoia > If a record has has_many associations defined AND those associations have dependent: :destroy set…
comment by dubswithus · 2022-07-20 · in Soft deletion probably isn't worth it -
https://github.com/rubysherpas/paranoia is enough to solve problems at very large scales. There is nothing about Rails or MVC preventing someone from doing this. This is a very common design principle for all kind of ERP and BPM systems:…
comment by legedemon · 2022-04-15 · in We lost 54k GitHub stars -
…how much time you have. Ruby has a lot of gems, but many of them are buggy and deprecated... Proof: https://github.com/rubysherpas/paranoia I think that Elixir is gonna catch up. If you write a project where you need to use a lot of…
comment by wrestlerman · 2019-03-19 · in Why I believe Rails is still relevant in 2019 -
…is involved and there is a reason to worry about data being retained as a bad thing. For Rails: https://github.com/rubysherpas/paranoia For Laravel: https://laravel.com/docs/5.3/eloquent#soft-deleting
comment by saluki · 2016-08-30 · in Ask HN: Should I let clients delete their data? -
There is a popular Ruby gem which addresses this sort of concern: https://github.com/rubysherpas/paranoia Essentially it doesn't delete but gives the impression to the user that it deletes. I like this idea because it really does guard…
comment by patrickgordon · 2016-08-30 · in Ask HN: Should I let clients delete their data?