Migration to segregate compliance checks resources#187
Merged
UlisesGascon merged 10 commits intomainfrom Jan 23, 2025
Merged
Conversation
- create new table compliance_checks_resources - create new relation table resources_for_compliance_checks - populate both tables out of the data existing in compliance_checks table - drop pointless columns in compliance_checks table
This comment was marked as resolved.
This comment was marked as resolved.
UlisesGascon
added a commit
that referenced
this pull request
Jan 23, 2025
Co-authored-by: Guillermo C. Martínez <telekosmos@ymail.com>
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Main Changes
This PR includes all the great work donde by @telekosmos in #183 with some minor changes (like file renames, remove specific tests, etc..) and includes all the new resources (collected via scripting and included in the migrations).
I will work in a separate PR to adapt
db:export-checksto the new segregation format.Context
compliance_checks_resourcestable #141