Add Databricks DDL for OMOP CDM v5.4
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.1k
- Forks
- 508
- Avg merge
- 1h 30m
- Merged PRs (30d)
- 3
Description
Hello, I've created Databricks-compatible DDL scripts for OMOP CDM v5.4. These scripts support Unity Catalog with USE CATALOG / USE SCHEMA for deployment flexibility.
Scripts
Three files:
- OMOPCDM_databricks_5.4_ddl.sql - All 39 CREATE TABLE statements
- OMOPCDM_databricks_5.4_primary_keys.sql - 30 primary key constraints
- OMOPCDM_databricks_5.4_constraints.sql - 89 foreign key constraints
OMOPCDM_databricks_5.4_primary_keys.sql
OMOPCDM_databricks_5.4_ddl.sql
OMOPCDM_databricks_5.4_constraints.sql
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the attached OMOPCDM_databricks_5.4_ddl.sql, OMOPCDM_databricks_5.4_primary_keys.sql, and OMOPCDM_databricks_5.4_constraints.sql files against the repository’s existing OMOP CDM v5.4 DDL conventions. Check that the 39 tables, 30 primary keys, 89 foreign keys, and Unity Catalog statements are consistent and Databricks-compatible. Done means the three scripts are added in the expected locations and can be deployed with USE CATALOG and USE SCHEMA.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100