Skip to main content

ChEMBL PostgreSQL



With the aim of providing more options to access the ChEMBL database, a PostgreSQL version of the most recent ChEMBL release is now available on the ChEMBL FTP site, (thanks to the Ora2Pg project for making the conversion process relatively painless). 

The main goal of this project is make it easier for users to integrate the chemical data in the ChEMBL database with freely available chemical cartridges, such as the excellent RDKit and Bingo. Now that we have the PostgreSQL version of the database available, we are in the process of benchmarking the aforementioned chemical cartridges - we will report back soon the results of the benchmarking exercises we are undertaking. We are also looking to build and release a virtual machine, which will come preloaded with ChEMBL, PostgreSQL, RDKit and/or Bingo. When we have more details on this we will let you know.

Right now everyone has the opportunity to download and install the PostgreSQL version of the ChEMBL database and optionally install a chemical cartridge. We hope this will help as many projects as possible and any comments or feedback will be very much appreciated. Enjoy it :)

(You can download the ChEMBL_14 PostgreSQL here, the tarball also comes with some basic install instructions, but does assume you have a PostgreSQL instance up and running).

Comments

greg landrum said…
Nice!

Let me know if there's anything I can do to help with the benchmarking.
Unknown said…
oh yes, you'll hear from us soon
:)
greg landrum said…
Any chance you would be willing/able to share logs of substructures that people have executed against ChEMBL?

That kind of real-world (and public) data would be very helpful for optimizing SSS fingerprints.
jpo said…
Greg - we've been asked this a lot of times, and quite simply it's against our terms of use of the resources here at the EBI. The queries are confidential, and we have written the application, so anything that may be considered confidential is cleared from any caches as soon as is practicable, consistent with reasonable performance, or is only stored client side.

In summary, we don't store the queries.

There have been a few apocryphal cases where in the field of drug discovery, people have gone and mined or shared the queries of their web resources, and it is quite a sad tale......
Kyle Kinney said…
Awesome, this is almost exactly what I needed - I was not looking forward to trying to convert this into postgresql myself. There's only one little issue - I'm running postgresql 9.0, and this is for postgresql 9.1. Any idea what kinds of compatibility issues am I likely to run into? The only noticeable failure I saw on loading was the failure of the CREATE EXTENSION plpgsql, and I may or may not be able to substitute CREATE LANGUAGE there. Not sure how much plpgsql has changed between versions, other than being an extension now.
Push comes to shove, I can migrate, but if it's a matter of changing a couple lines at the top, I'd rather avoid it.

Popular posts from this blog

New SureChEMBL announcement

(Generated with DALL-E 3 ∙ 30 October 2023 at 1:48 pm) We have some very exciting news to report: the new SureChEMBL is now available! Hooray! What is SureChEMBL, you may ask. Good question! In our portfolio of chemical biology services, alongside our established database of bioactivity data for drug-like molecules ChEMBL , our dictionary of annotated small molecule entities ChEBI , and our compound cross-referencing system UniChem , we also deliver a database of annotated patents! Almost 10 years ago , EMBL-EBI acquired the SureChem system of chemically annotated patents and made this freely accessible in the public domain as SureChEMBL. Since then, our team has continued to maintain and deliver SureChEMBL. However, this has become increasingly challenging due to the complexities of the underlying codebase. We were awarded a Wellcome Trust grant in 2021 to completely overhaul SureChEMBL, with a new UI, backend infrastructure, and new f

ChEMBL & SureChEMBL anniversary symposium

  In 2024 we celebrate the 15th anniversary of the first public release of the ChEMBL database as well as the 10th anniversary of SureChEMBL. To recognise this important landmark we are organising a two-day symposium to celebrate the work achieved by ChEMBL and SureChEMBL, and look forward to its future.   Save the date for the ChEMBL 15 Year Symposium October 1-2, 2024     Day one will consist of four workshops, a basic ChEMBL drug design workshop; an advanced ChEMBL workshop (EUbOPEN community workshop); a ChEMBL data deposition workshop; and a SureChEMBL workshop. Day two will consist of a series of talks from invited speakers, a few poster flash talks, a local nature walk, as well as celebratory cake. During the breaks, the poster session will be a great opportunity to catch up with other users and collaborators of the ChEMBL resources and chat to colleagues, co-workers and others to find out more about how the database is being used. Lunch and refreshments will be pro

ChEMBL 34 is out!

We are delighted to announce the release of ChEMBL 34, which includes a full update to drug and clinical candidate drug data. This version of the database, prepared on 28/03/2024 contains:         2,431,025 compounds (of which 2,409,270 have mol files)         3,106,257 compound records (non-unique compounds)         20,772,701 activities         1,644,390 assays         15,598 targets         89,892 documents Data can be downloaded from the ChEMBL FTP site:  https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_34/ Please see ChEMBL_34 release notes for full details of all changes in this release:  https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_34/chembl_34_release_notes.txt New Data Sources European Medicines Agency (src_id = 66): European Medicines Agency's data correspond to EMA drugs prior to 20 January 2023 (excluding vaccines). 71 out of the 882 newly added EMA drugs are only authorised by EMA, rather than from other regulatory bodies e.g.

RDKit, C++ and Jupyter Notebook

Fancy playing with RDKit C++ API without needing to set up a C++ project and compile it? But wait... isn't C++ a compiled programming language? How this can be even possible? Thanks to Cling (CERN's C++ interpreter) and xeus-cling jupyter kernel is possible to use C++ as an intepreted language inside a jupyter notebook! We prepared a simple notebook showing few examples of RDKit functionalities and a docker image in case you want to run it. With the single requirement of docker being installed in your computer you'll be able to easily run the examples following the three steps below: docker pull eloyfelix/rdkit_jupyter_cling docker run -d -p 9999:9999 eloyfelix/rdkit_jupyter_cling open  http://localhost:9999/notebooks/rdkit_cling.ipynb  in a browser

A python client for accessing ChEMBL web services

Motivation The CheMBL Web Services provide simple reliable programmatic access to the data stored in ChEMBL database. RESTful API approaches are quite easy to master in most languages but still require writing a few lines of code. Additionally, it can be a challenging task to write a nontrivial application using REST without any examples. These factors were the motivation for us to write a small client library for accessing web services from Python. Why Python? We choose this language because Python has become extremely popular (and still growing in use) in scientific applications; there are several Open Source chemical toolkits available in this language, and so the wealth of ChEMBL resources and functionality of those toolkits can be easily combined. Moreover, Python is a very web-friendly language and we wanted to show how easy complex resource acquisition can be expressed in Python. Reinventing the wheel? There are already some libraries providing access to ChEMBL d