[ensembl-dev] database model and API versions

[Duarte Molha]

Dear developers

On your GRCh37 archive site you say this:

===========================

About this archive

This archive is based on Ensembl Release 75 data, and gives continuing
access to human assembly GRCh37, as well as all our other release 75
species (data freeze March 2014) for comparative purposes. Human variation
and regulation data has since been updated in March 2015.

The API and website will be updated in tandem with the release of the main
Ensembl website (*currently version 79*), and we will also periodically
update this site with new data human, which will be announced in this panel.
MySQL dumps of human databases on the most recent schema version are
available on our FTP site <ftp://ftp.ensembl.org/pub/grch37/>.

=========================

It was my understanding that an API version was directly linked to a
specific assembly. So I thought that if I wanted to query the latest GRCh37
assembly I would need to use the api v75 and if I wanted to use a local
database, I would download the corresponding sql tables for that version.

However, according to this announcement, I can now use the V79 api and
query the old assembly... How is this accomplished ?
What you I have to do on my scripts to make sure I am querying the 37
version even though I am using the latest API?

Sorry, I hope this is not a stupid question but I am a bit confused.

Best regards

Duarte



=========================
     Duarte Miguel Paulo Molha
         http://about.me/duarte
=========================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ensembl.org/pipermail/dev_ensembl.org/attachments/20150427/d3de2380/attachment.html>