You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 9, 2024. It is now read-only.
SQLite vs MySQL
I have been storing the inchi keys of PubChem in a SQlite database, this should contain the majority of compounds in PubChem and is used to extract inchi keys from PubChem compound ids (cid).
However, I think the SQLite database is better if it is integrated fully into the Django database. Before this is done however, performance should be assessed as this will drastically increase the number of Compounds within the database and as the uid is an inchikey I am not sure how indexing will be affected.
Updated details
When creating the SQLite database the parsing tool I used failed for some non normal mol files. As such some compounds are missing. This needs to be repeated but it takes a long time to run due to number of PubChem cmpounds
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
SQLite vs MySQL
I have been storing the inchi keys of PubChem in a SQlite database, this should contain the majority of compounds in PubChem and is used to extract inchi keys from PubChem compound ids (cid).
However, I think the SQLite database is better if it is integrated fully into the Django database. Before this is done however, performance should be assessed as this will drastically increase the number of Compounds within the database and as the uid is an inchikey I am not sure how indexing will be affected.
Updated details
When creating the SQLite database the parsing tool I used failed for some non normal mol files. As such some compounds are missing. This needs to be repeated but it takes a long time to run due to number of PubChem cmpounds
The text was updated successfully, but these errors were encountered: