- 03 Dec, 2019 1 commit
-
-
Uwe Kubosch committed
-
- 02 Dec, 2019 5 commits
-
-
Uwe Kubosch committed
-
Uwe Kubosch committed
-
Uwe Kubosch committed
-
Uwe Kubosch committed
-
`gem update --system` fails with Ruby 2.2.
Uwe Kubosch committed
-
- 26 Apr, 2019 1 commit
-
-
John Hawthorn committed
-
- 22 Apr, 2019 9 commits
-
-
Activerecord 6 support
John Hawthorn committed -
Jared Norman committed
-
Jared Norman committed
-
The versions we were running against were bumped, so we needed to update which versions were being excluded as they were stale. Rails master (soon to be 6.0.0) doesn't support versions before Ruby 2.5.
Jared Norman committed -
These versions of rails enforce this version constraint when loading the sqlite adapter so we need to make sure that we always use a compatible version.
Jared Norman committed -
Older versions of activerecord require sqlite ~> 1.3.6, but not in the gemfile, the constraint is enforced when you load the adapter. This allows us toe specify in the environment the version of the gem we'd like to run against.
Jared Norman committed -
Anton Kolodii committed
-
Anton Kolodii committed
-
We are trying to test our application on rails 6.0.0.alpha but we can't install this because of the version lock Probably this will be helpful that we can try and report any issues with edge rails
Anton Kolodii committed
-
- 07 Mar, 2019 1 commit
-
-
Add Ruby 2.6 to Travis CI.
Rebecca Le committed
-
- 15 Feb, 2019 1 commit
-
-
Jun Aruga committed
-
- 11 Apr, 2018 2 commits
-
-
Fix typo (`6.2.0` -> `5.2.0`)
John Hawthorn committed -
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
-