Refactor: remove organism_grouping_key from schema#19
Merged
Conversation
…axon_id as PK instead
…axon_id as PK instead
…match atol schema
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
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.
📌 Summary
Remove
organism.grouping_keyfrom the database schema and usetaxon_idinstead, to reflect changes to the data mapper's output.taxon_idis a natural choice for PK on organism table, since it is unique and must exist for all organisms.🔄 Type of Change
🧩 Key Changes
grouping_keyfromorganismtable and maketaxon_idthe PK and 2) update any FK references to theorganismtable to referencetaxon_id✅ Checklist
🔍 Review Notes
📎 Related Issues / Tickets