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

ddl postgres issues #98

Closed
mattlevine22 opened this issue Aug 4, 2017 · 3 comments
Closed

ddl postgres issues #98

mattlevine22 opened this issue Aug 4, 2017 · 3 comments
Assignees
Labels

Comments

@mattlevine22
Copy link

mattlevine22 commented Aug 4, 2017

I'm trying to set up the cdm in postgres, and have run into a few issues, some of which others have mentioned. I'll consolidate them here--let me know if they should be broken out into separate issues.

  1. ddl on Postgres #96 There is an issue with the naming of "offset" in the note_nlp table in the DDL postgres file.
  2. ddl postgres visit_occurrence.discharge_to_concept_id bug #97 There is a bug in the declaration of "discharge_to_concept_id" in the visit_occurrence table in the DDL postgres file. It is defined as "INTEGER(50)", and should probably just be INTEGER.
  3. In constraints postgres file, there is a syntax error in line 129 caused by the word "NONCLUSTERED". I assume the appropriate fix is to just remove that word.
  4. In indexes required postgres file, there is a reference to "person_id" in the note_nlp table, but person_id is not defined in the note_nlp table by the ddl file. Perhaps person_id needs to be added to that table in the ddl file.
  5. In constraints postgres file, the foreign key "dose_unit_concept_id" does not exist in the DDL postgres file. (the closest thing i could find in the ddl file is "dose_unit_source_value", which, coincidentally, is not referenced in the constraints file).
@clairblacketer
Copy link
Contributor

@mattlevine22 thank you so much for highlighting these. Some of these issues could also be issues with the other ddls so I will take a look at all of them to be safe.

@clairblacketer clairblacketer self-assigned this Aug 7, 2017
@bobml
Copy link

bobml commented Aug 7, 2017

I would have to concur with mattlevine22 also, I encountered all of these issues as well.

@vojtechhuser
Copy link
Collaborator

vojtechhuser commented Aug 8, 2017

I made PR that fixes the integer(50) problem 3 days prior this report.

clairblacketer added a commit that referenced this issue Aug 8, 2017
…Postgresql but similar issues were found in oracle, impala and sql server files.
clairblacketer added a commit that referenced this issue Aug 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants