Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

98 duplicate acsn bug resolved #105

Merged
merged 2 commits into from
Jul 31, 2023
Merged

98 duplicate acsn bug resolved #105

merged 2 commits into from
Jul 31, 2023

Conversation

cthunes
Copy link
Contributor

@cthunes cthunes commented Jul 26, 2023

Duplicates acsn's have been removed from the assay_component_map table and the acsn column was given the UNIQUE constraint.

Added a check within tcplRegister for catching error and created output message if duplicates are attempted to be registered.

> tcplRegister(what = "acsn", flds = list(acid = 2938, acsn = "tox21-ror-cho-viability-p1_set1"))
acsn was not inserted into the database:
Duplicate entry 'tox21-ror-cho-viability-p1_set1' for key 'acsn' [1062]
Duplicate values are not permitted; this source may already be registered!
[1] FALSE

Closes #98.

@cthunes cthunes self-assigned this Jul 26, 2023
@cthunes cthunes merged commit d76383d into main Jul 31, 2023
1 check passed
@cthunes cthunes deleted the 98-duplicate-acsn-bug branch July 31, 2023 13:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Avoid writing duplicate acsns when they are already in the database
2 participants