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

[Daniel Barrell]

Hi Jeremy,

It seems that the core team patched up the schema for 73 whilst running 
xrefs. This can happen if the database schema does not match the schema 
the code uses whenn they come to run their scripts. For release 74 they 
did not need to patch the code so it remained as it was when it was 
created. Knowing this we can assume that the current ccds database will 
always work with the branch of code for that release so you should never 
find incompatabilities.

So, to confirm, if you need to find the schema version you have to 
retrieve this from the meta table.

Regards

Dan


On 25/11/13 16:00, Jeremy Henty wrote:
> Daniel Barrell wrote:
>
>> Occasionally, a database has been patched when a significant schema
>> change means it will not work with the code release it is intended
>> for, hence the discrepancy in human 73. However, I need to look into
>> why release 74 uses schema 72, it may need to be patched up.
> What did you find?  We are always keen to use the latest CCDS release
> but if it's an old (and possibly incompatible) schema version then we
> have to hold back, which is a shame.
>
> Jeremy Henty
> Anacode Team
>
> _______________________________________________
> Dev mailing list    Dev at ensembl.org
> Posting guidelines and subscribe/unsubscribe info: http://lists.ensembl.org/mailman/listinfo/dev
> Ensembl Blog: http://www.ensembl.info/