Compounds
Name
Compound type
Version
Size
File
Compounds (csv)
original
01.2025
56.57 MB
Compounds (csv)
standardized
01.2025
48.96 MB
Compounds (csv)
nonisomeric
01.2025
39.79 MB
Compounds (sdf)
original
01.2025
408.85 MB
Compounds (sdf)
standardized
01.2025
349.7 MB
Compounds (sdf)
nonisomeric
01.2025
303.92 MB
Targets & activities
Name
Compound type
Version
Size
File
Targets and activities (csv)
original
01.2025
84.05 MB
Targets and activities (csv)
standardized
01.2025
83.6 MB
Targets and activities (csv)
nonisomeric
01.2025
82.34 MB
Targets and activities (xlsx)
original
01.2025
48.54 MB
Targets and activities (xlsx)
standardized
01.2025
44.67 MB
Targets and activities (xlsx)
nonisomeric
01.2025
39.85 MB
Chemical probes
Name
Compound type
Version
Size
File
Chemical probes (xlsx)
standardized
01.2025
2.01 MB
Compound ID mapping
Name
Compound type
Version
Size
File
Compound ID mapping (csv)
original
01.2025
35.48 MB
Compound ID mapping (csv)
standardized
01.2025
31.42 MB
Compound ID mapping (csv)
nonisomeric
01.2025
24.39 MB
Database dump
Name
Version
Size
File
PostgreSQL database dump (zip)
01.2025
186.89 MB
SQLite database (zip)
01.2025
296.26 MB
# To restore the data from the PostgreSQL dump, first, you need to extract (unzip) the dump and create an empty database:
CREATE DATABASE database_name WITH OWNER username;
# Then you can restore the dump using:
pg_restore --no-owner -h HOST -p PORT -U USERNAME -d database_name /path/to/pd_dump.sql
Please be aware that internal database IDs are not preserved and may change from version to version. The only IDs that are consistently preserved are compounds' PDIDs, which can be used to link to P&D.