- 11 Apr, 2018 1 commit
-
-
Shuichi Tamayose committed
-
- 10 Apr, 2018 2 commits
-
-
Version 2.4.1
John Hawthorn committed -
John Hawthorn committed
-
- 09 Apr, 2018 1 commit
-
-
John Hawthorn committed
-
- 04 Apr, 2018 1 commit
-
-
Improvements to rails 5.2 patches
John Hawthorn committed
-
- 29 Mar, 2018 3 commits
-
-
John Hawthorn committed
-
John Hawthorn committed
-
John Hawthorn committed
-
- 28 Mar, 2018 2 commits
-
-
John Hawthorn committed
-
Monkeypatch activerecord relations to work with rails >=5.2.0rc2
Ben A. Morgan committed
-
- 23 Mar, 2018 1 commit
-
-
Bartosz Bonisławski committed
-
- 09 Jan, 2018 3 commits
-
-
Test new ruby versions
Ben A. Morgan committed -
Nicolas Leger committed
-
Nicolas Leger committed
-
- 05 Jan, 2018 3 commits
-
-
Add a very soft deprecation notice
John Hawthorn committed -
This isn't a change from how paranoia has been developed for the past few years, but makes it more explicit. I hope the recommendation against new projects using paranoia isn't too controversial. I think anyone who has used this gem extensively has been surprised by it many times. This is just the nature of replacing ActiveRecord's behaviour. I believe paranoia does extremely well given that it does that. A lot of developers will reach for paranoia or acts_as_paranoid because they're the first result they will find. However most users are just looking to hide or disable some records, and they would do much better to just toggle a flag rather than have paranoia override ActiveRecord's behaviour on their model. I hope linking to discard here isn't inappropriate, I believe it's the best resource describe the caveats of paranoia as well as give a good example of how to soft-delete without needing paranoia or acts_as_paranoid.
John Hawthorn committed -
Test with Rails 5.2
John Hawthorn committed
-
- 29 Nov, 2017 1 commit
-
-
Patrik Bóna committed
-
- 03 Nov, 2017 3 commits
-
-
Version 2.4.0
John Hawthorn committed -
John Hawthorn committed
-
Add paranoia_destroy and paranoia_delete aliases
John Hawthorn committed
-
- 02 Nov, 2017 10 commits
-
-
John Hawthorn committed
-
Version-related cleanup
John Hawthorn committed -
John Hawthorn committed
-
Rebase of #412
John Hawthorn committed -
This removes the assumption from `really_destroy!` that there is only one column value, the deletion date, that needs to be updated on a model that is being `really_destroy!`ed. Instead, use the defined `paranoia_destroy_attributes` as they are used in `destroy` and other calls. This prevents an issue where the DBMS will complain when trying to `really_destroy!` one of these models, given that paranoia is attempting to insert a DateTime value into a boolean (or otherly- typed) column. Fixes #326
Steve Rice committed -
John Hawthorn committed
-
This makes paranoia's code itself more explicit.
John Hawthorn committed -
This should help users be more explicit about what action they want to perform. My hope is that this will also make it easier to migrate off of paranoia.
John Hawthorn committed -
John Hawthorn committed
-
John Hawthorn committed
-
- 01 Nov, 2017 2 commits
-
-
John Hawthorn committed
-
John Hawthorn committed
-
- 08 Aug, 2017 2 commits
-
-
Update .travis.yml
Ben A. Morgan committed -
Removed the pessimistic dependency requirements. Updated Ruby versions. Test paranoia with Rails 5.1
Anton Rieder committed
-
- 31 May, 2017 1 commit
-
-
⚠ instance variable @_disable_counter_cache not initializedBen A. Morgan committed
-
- 30 May, 2017 2 commits
-
-
This `defined?(super)` check was introduced for Rails 4.1 support https://github.com/rubysherpas/paranoia/pull/390#issuecomment-284819747 but we've stopped supporting Rails 4.1 already https://github.com/rubysherpas/paranoia/pull/393#issuecomment-289227091
Akira Matsuda committed -
⚠ Akira Matsuda committed
-
- 27 Apr, 2017 2 commits
-
-
Version 2.3.1
John Hawthorn committed -
John Hawthorn committed
-