[ensembl-dev] Surprising CCDS schema versions: mismatches with the version in the database name.

Jeremy Henty jh13 at sanger.ac.uk
Fri Nov 15 16:29:28 GMT 2013


I am surprised that several of the CCDS databases have schema versions
that do not match what you would expect from their name.

    ccds_human_71: name version = '71', db version = '70'
    ccds_human_74: name version = '74', db version = '72'
    ccds_mouse_71: name version = '71', db version = '70'
    ccds_mouse_73: name version = '73', db version = '71'
    ccds_mouse_74: name version = '74', db version = '73'

Since the schema version of ccds_human_73 is 73 as you would expect
this means the schema version went *backwards* from ccds_human_73 to
ccds_human_74 !

Is there a reason for this?  It would make scripting easier if we
could reliably infer the schema version from the name.

Jeremy Henty
Anacode team
Wellcome Trust Sanger Institute




More information about the Dev mailing list