-
Notifications
You must be signed in to change notification settings - Fork 46
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
add unique key constraint on Phenotype table #304
Comments
@gedankenstuecke I am going to assume that since we have a validation step at the controller stage there will be no duplicate entries in the |
@vivekiitkgp I think there were like 2-3 duplicate phenotypes which would have to be manually dealt with before. Thanks for the work on it so far! |
I'd prefer that we deal with it through a reviewable and testable migration over fiddeling around with it manually. ;) |
Fair enough :p |
@tsujigiri On it! |
Following from discussion on gitter.
The text was updated successfully, but these errors were encountered: