Bi-directional cachinig of transcript-protein links
Previously transcript-protein links were assumed to always be indexed by transcript, and cached entries were allowed to have a `null` protein (meaning caching the knowledget that there is no link for this transcript). Now we can cache links in both directions. Both transcript and protein are allowed to be `null` (but not at the same time), and the protein column has a new unique constraint.
Showing
- doc/config.rst 2 additions, 2 deletionsdoc/config.rst
- migrations/versions/3492d2ee8884_transcript_protein_links_have_nullable_.py 59 additions, 0 deletions...s/3492d2ee8884_transcript_protein_links_have_nullable_.py
- mutalyzer/config/default_settings.py 2 additions, 2 deletionsmutalyzer/config/default_settings.py
- mutalyzer/db/models.py 9 additions, 5 deletionsmutalyzer/db/models.py
- mutalyzer/db/queries.py 50 additions, 18 deletionsmutalyzer/db/queries.py
Please register or sign in to comment