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

add unique key constraint on Phenotype table #304

Open
raivivek opened this issue Jun 15, 2016 · 5 comments
Open

add unique key constraint on Phenotype table #304

raivivek opened this issue Jun 15, 2016 · 5 comments

Comments

@raivivek
Copy link
Member

Following from discussion on gitter.

@raivivek
Copy link
Member Author

@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 Phenotype table right now. If not, then one may have to operate on the table and merge duplicate entries...

@gedankenstuecke
Copy link
Member

@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!

@tsujigiri
Copy link
Collaborator

I'd prefer that we deal with it through a reviewable and testable migration over fiddeling around with it manually. ;)

@gedankenstuecke
Copy link
Member

Fair enough :p

@raivivek
Copy link
Member Author

@tsujigiri On it!

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

No branches or pull requests

3 participants