-
Notifications
You must be signed in to change notification settings - Fork 456
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
Missing foreign key constraints #16
Comments
Thanks, @bruth. Will check it out. |
Hi @clairblacketer. My organization maintains a repo of data models here which includes OMOP. That repository is consumed by two services we host, one that renders the data models as browsable web pages and one that provides SQL DDL generation. This is all dynamic and driven by the files in the repository we maintain. |
And to answer your question.. I am not sure if it was updated in this repo, but once we setup the data models repo, we have been updating and using that as the source of code generation. |
This is nice. We should adopt this. How do you actually do it behind the scenes? |
@bruth As far as updating versions, we maintain CSV files for each CDM release. These files are broken down into:
We update the CSVs for new columns or changes to columns etc so it still requires some human intervention. The service itself then validates the referential integrity. The DDL is then generated from these files. @aaron0browne will be able to speak to the more technical piece (sql alchemy etc) of how that is done. I apologize for the delay! |
closing this as the initial issue has been fixed |
The following foreign key constraints are not in the DDL files:
The text was updated successfully, but these errors were encountered: