GitLab

  We know that fetch_all_by_Transcript() (on a TranslationAdaptor) will
  return a list of translations, where the first one will always be the
  canonical translation (if there is one).  Make use of this fact to
  make the routine slightly quicker.

  * Use fetch_all_by_Transcript() rather than translation() on the
    transcript to get the canonical translation (and any alternative
    translations).

  * ... then store the translation and any alternative translations.

Solves a problem stopping genebuilders from copying genes from one
database to another.

  * Correct documentation.
  * Use fetch_by_Transcript() to get canonical translation.
  * Modify SQL not to get canonical translation.

get_all_alternative_translations().

  * In the _list_dbIDs() method: Wrap the execute() in an eval() and
    throw() if it fails.

  * In the generic_fetch() method: For multi-species databases, make
    sure we're using the correct SQL table aliases for the seq_region
    and coord_system tables..

like "aspergillus_fumigatusa1163_core_5_58_1a"
(containing integers as part of the second part
of their names).

transcript does not have an associated adaptor.

associated with the transcript.

  Args       : None
  Example    :

    my @alt_translations =
      @{ $transcript->get_all_alternative_translations() };

  Description:  Fetches all alternative translations defined for this
                transcript.  The canonical translation is not returned.

  Returntype : Array reference to Bio::EnsEMBL::Translation
  Exceptions : None
  Caller     : General
  Status     : Stable


Added method add_alternative_translation():

  Args       : Bio::EnsEMBL::Translation $translation
  Example    :

    $transcript->add_alternative_translation($translation);

  Description: Adds an alternative translation to this transcript.
  Returntype : None
  Exceptions : None
  Caller     : General
  Status     : Stable

"missing".

get fetch all to ignore LRG_gene this makes it slower but if you are getting all the them then this will be insignificant time difference

if more than one projection then check against the slcie you are projecting too to make sure it is the corect one. This is for multiple assemblys where a feature can go to nmore then one slice