-
Notifications
You must be signed in to change notification settings - Fork 196
Issues: ActsAsParanoid/acts_as_paranoid
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
SystemStackError during destroy with ActiveStorage 5.2
known issue
#103
opened May 4, 2018 by
domcleal
run_callback consumes the errors and it's hard to find out why recovering a record failed
#118
opened Mar 22, 2019 by
shadydealer
Callbacks due to :dependent options have potentially unintended effect
#128
opened Sep 16, 2019 by
mvz
Failing to recover parent but has_one association gets recovered
#130
opened Sep 24, 2019 by
frostblooded
Destroy method has unexpected behavior with ActiveModel::Dirty
#134
opened Oct 21, 2019 by
valeriecodes
Destroying fully doesn't honor dependent: :destroy, causing foreign key violation
bug
#142
opened Dec 17, 2019 by
kirykr
Recovery of dependent records fails due to validation error
bug
#166
opened Jun 29, 2020 by
thebravoman
Order of before_destroy and acts_as_paranoid should not really matter
bug
#168
opened Jun 29, 2020 by
thebravoman
after_commit on destroy only called for soft destroy on rails 6
#195
opened Jan 7, 2021 by
thijsnado
destroy_fully! does not perform real deletion at once. Performance issue.
#203
opened Feb 25, 2021 by
pilgunboris
Rails 6 issues with only_deleted with_deleted scopes
bug
more info needed
#205
opened Mar 2, 2021 by
unlimit
Behavior of destroy on associations does not match default ActiveRecord
#224
opened Apr 25, 2021 by
mvz
Add an option to update the timestamp when a record is logically deleted
#349
opened Oct 7, 2024 by
sukumo28
Previous Next
ProTip!
Follow long discussions with comments:>50.