Skip to content

Support for releases without the stable_id tables #12

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

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

homonecloco
Copy link

Hi Jan,
I just added code to fix the find_by_stable_id functions and stable_id properties in exon, gene, transcript and translation, to support the changes introduced in schema 65. I ran the test for version 60 to see if I didnt brake anything, and seems ok. I also added tests for the functions I changed calling the ensemble genes version 70. Originally, I intended to use the release from the get_info method, but I found it would complicate the version on ensemble genomes, as the release are not the same as the API version there. So I coded a function that detects if the stable_id tables are present or not, and store that as a class variable in the Base. That is reset each time a new connection is done. So, the overhead of detecting which version of the code shouldn't be noticeable.
Fixes: #11

Cheers
Ricardo.

@homonecloco
Copy link
Author

Ah, and I forgot to mention. I updated the code to stop using set_primary_key to self.primary_key to use the latest conventions on active record.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Compatibility issues with schemas 65+
1 participant