Tweak handling of gene family data#174
Merged
TamaraNaboulsi merged 1 commit intoJul 20, 2026
Merged
Conversation
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
2 participants
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.
Gene family views can take some time to load, particularly for large families.
This pull request would make some adjustments to handling of family data, with the aim of reducing access times.
In
EnsEMBL::Web::Object::Gene::filtered_family_data, instead of combining a Compara Perl API call and MySQL query,we would fetch all the standard family data with a single query.
In
EnsEMBL::Web::Component::Gene::GeneFamilySeq, instead of combining data fetched via the Compara Perl API with the results ofEnsEMBL::Web::Object::Gene::filtered_family_data, we would use a modified version offiltered_family_datawhich enables us to fetch the translation sequence alongside standard family data.Examples: