<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Luke,<br>
<br>
The registry can only deal with one core database for one species
and release at a time.<br>
It currently does not distinguish based on the assembly.<br>
So if you use the API with the registry
($registry->load_registry_from_db), you will not be able to have
two versions of the same species database.<br>
<br>
However, if you explicitly connect to one database, it is possible.<br>
For example:<br>
my $dba = Bio::EnsEMBL::DBSQL::DBAdaptor->new(<br>
-HOST => 'ensembldb.ensembl.org',<br>
-PORT => 3306,<br>
-USER => 'anonymous',<br>
-SPECIES => 'homo_sapiens_38',<br>
-DBNAME => 'homo_sapiens_core_84_38',<br>
-GROUP => 'core'<br>
);<br>
will create a database adaptor for the GRCh38 human database.<br>
and <br>
my $dba = Bio::EnsEMBL::DBSQL::DBAdaptor->new(<br>
-HOST => 'ensembldb.ensembl.org',<br>
-PORT => 3337,<br>
-USER => 'anonymous',<br>
-SPECIES => 'homo_sapiens_37',<br>
-DBNAME => 'homo_sapiens_core_84_37',<br>
-GROUP => 'core'<br>
);<br>
will create a database adaptor for the GRCh37 human database.<br>
You can then use both databases within the same code.<br>
<br>
Note here that I named the species homo_sapiens_38 and
homo_sapiens_38, otherwise the new adaptor will supersed the old
one.<br>
Similarly, if you also have a load_registry_from_db call in your
code, this will have already loaded a human core database and that
will be the one used by default.<br>
<br>
If you do not use the two databases within the same code, you can
simply keep the homo_sapiens species alias, although again, without
another load_registry_from_db call.<br>
<br>
<br>
Hope that helps,<br>
Magali<br>
<br>
<div class="moz-cite-prefix">On 14/03/2016 20:46, Luke Goodsell
wrote:<br>
</div>
<blockquote
cite="mid:59C49FE16E416F46873F86D530DA8052177DF8@ExchangeServer.internal.ogtip.com"
type="cite">
<pre wrap="">Hi,
Is it possible to load both the same releases of the GRCh37 and GRCh38 EnsEMBL databases on the same server and choose which assembly to use in the Perl API? We currently have them running on different mysqld instances, but this is undesirable.
I understand I could keep release n of 38 and release n-1 of 37, and load the corresponding perl modules, but this would quickly become a nightmare to maintain as new releases come out.
Kind regards,
Luke
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Dev mailing list <a class="moz-txt-link-abbreviated" href="mailto:Dev@ensembl.org">Dev@ensembl.org</a>
Posting guidelines and subscribe/unsubscribe info: <a class="moz-txt-link-freetext" href="http://lists.ensembl.org/mailman/listinfo/dev">http://lists.ensembl.org/mailman/listinfo/dev</a>
Ensembl Blog: <a class="moz-txt-link-freetext" href="http://www.ensembl.info/">http://www.ensembl.info/</a>
</pre>
</blockquote>
<br>
</body>
</html>