This involves making the SQLAlchemy session reconfigurable at run-time,
which is done automatically on updating the Mutalyzer configuration using
configuration update callbacks.

git-svn-id: https://humgenprojects.lumc.nl/svn/mutalyzer/trunk@664 eb6bd6ab-9ccd-42b9-aceb-e2899b4a52f1

git-svn-id: https://humgenprojects.lumc.nl/svn/mutalyzer/trunk@639 eb6bd6ab-9ccd-42b9-aceb-e2899b4a52f1

git-svn-id: https://humgenprojects.lumc.nl/svn/mutalyzer/trunk@573 eb6bd6ab-9ccd-42b9-aceb-e2899b4a52f1

git-svn-id: https://humgenprojects.lumc.nl/svn/mutalyzer/trunk@572 eb6bd6ab-9ccd-42b9-aceb-e2899b4a52f1

git-svn-id: https://humgenprojects.lumc.nl/svn/mutalyzer/trunk@570 eb6bd6ab-9ccd-42b9-aceb-e2899b4a52f1

git-svn-id: https://humgenprojects.lumc.nl/svn/mutalyzer/trunk@567 eb6bd6ab-9ccd-42b9-aceb-e2899b4a52f1

git-svn-id: https://humgenprojects.lumc.nl/svn/mutalyzer/trunk@558 eb6bd6ab-9ccd-42b9-aceb-e2899b4a52f1

This fixes Trac bug #95.


git-svn-id: https://humgenprojects.lumc.nl/svn/mutalyzer/trunk@524 eb6bd6ab-9ccd-42b9-aceb-e2899b4a52f1

Until now, the name checker form used POST requests. As a special case for
linking from LOVD, GET requests were handled by showing results without the
full interface (header, menu, etc). Ordinary linking was done to a separate
checkForward location which then set a cookie with the variant name and a
redirect to the name checker results. This was all very hackish and somewhat
broken (see Track issue #94).

This commit refactors the name checker to use GET requests, so ordinary
bookmarking of result pages is possible. All old entrypoints are handled with
a redirect for backwards compatibility.

Worth mentioning is that variant descriptions in the name checker are now
limited in length by the maximum query string length. However, this maximum
is several thousand characters with Internet Explorer having the lowest
maximum of just over 2000. Longer descriptions are not practically checked
with the name checker web interface anyway, so this should not be a problem.


git-svn-id: https://humgenprojects.lumc.nl/svn/mutalyzer/trunk@521 eb6bd6ab-9ccd-42b9-aceb-e2899b4a52f1

git-svn-id: https://humgenprojects.lumc.nl/svn/mutalyzer/trunk@502 eb6bd6ab-9ccd-42b9-aceb-e2899b4a52f1

During import of the NCBI transcript mappings, CDS start or stop positions
were not picked up for some transcripts (where these are on exon boundaries).

Bug reported by S Venkata Suresh Kumar.


git-svn-id: https://humgenprojects.lumc.nl/svn/mutalyzer/trunk@490 eb6bd6ab-9ccd-42b9-aceb-e2899b4a52f1

git-svn-id: https://humgenprojects.lumc.nl/svn/mutalyzer/trunk@420 eb6bd6ab-9ccd-42b9-aceb-e2899b4a52f1

The old way of using the configuration file was by instantiating a Config
object which read the file. This instance was passed to every function and
object that might need it.

The new way is by simply calling config.get('name') to get the configuration
value for 'name'. This lazily reads the configuration file and the contents
are cached for future calls.


git-svn-id: https://humgenprojects.lumc.nl/svn/mutalyzer/branches/implicit-config-branch@408 eb6bd6ab-9ccd-42b9-aceb-e2899b4a52f1

Convert the 'hg18.map' and 'hg19.map' tables are to 'hg18.Mapping' and
'hg19.Mapping'. These tables are now updated with mapping info from the
NCBI instead of the UCSC.

Also added database and configuration file migration scripts.

extras/config.example:
- Remove configuration values for UCSC updates.

extras/post-install.sh:
mutalyzer/Mapper.py:
mutalyzer/Db.py:
- Use 'Mapping' table instead of 'map' table.

extras/cron.d/mutalyzer-mapping-update:
mutalyzer/Mapper.py:
mutalyzer/Db.py:
- Get mapping updates from the NCBI.

extras/migrations:
extras/post-upgrade.sh:
- Automated migration scripts.



git-svn-id: https://humgenprojects.lumc.nl/svn/mutalyzer/branches/refactor-mutalyzer-branch@342 eb6bd6ab-9ccd-42b9-aceb-e2899b4a52f1

git-svn-id: https://humgenprojects.lumc.nl/svn/mutalyzer/branches/refactor-mutalyzer-branch@338 eb6bd6ab-9ccd-42b9-aceb-e2899b4a52f1