[#61776] Configure active_record_doctor
to detect mismatched fk constraints and association dependent
option
#18075
+15
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ticket
https://community.openproject.org/wp/61776
also relates to bug https://community.openproject.org/wp/61708
What are you trying to accomplish?
dependent
option.dependent
option on twoUser
has_many
associations.dependent
option onUser
(or any other model) associations - this is open to discussion.Results
Details
Details
What approach did you choose and why?
I've looked at Active Record Doctor while working on a previous project and I've found it to provide quite useful information with regards to the health of the database schema.
Unfortunately AR Doctor's
rake active_record_doctor:incorrect_dependent_option
task only checks for cases whendependent:
is defined but not incorrect (because of the presence or absence of callbacks on the associated model). However used in conjunction with Rubocop'sHasManyOrHasOneDependent
cop, I still think this is a useful tool.Merge checklist