OMOP/PostgreSQL
Maxim Moinat b1629bf6bd
Fix in postgres readme
Steps 4 and 5 have to be performed in the reverse order. Namely, the (foreign key) constraints depend on the primary key created in the indexes file. This was probably introduced in the new DDL generator change.

Not sure whether this is also the case for other SQL languages.
2018-05-02 14:54:25 +02:00
..
VocabImport Reordered the folder structure 2015-03-18 22:48:13 -04:00
OMOP CDM postgresql constraints.txt Final cdm v5.3 addition, moved new DDLs to correct locations 2018-01-03 14:56:42 -05:00
OMOP CDM postgresql ddl.txt Merge branch 'master' into cdm_v5.3.-bugfix.2 2018-02-07 19:54:09 -05:00
OMOP CDM postgresql indexes.txt Final cdm v5.3 addition, moved new DDLs to correct locations 2018-01-03 14:56:42 -05:00
README.md Fix in postgres readme 2018-05-02 14:54:25 +02:00

README.md

Common-Data-Model / PostgreSQL

This folder contains the SQL scripts for PostgreSQL.

In order to create your instantiation of the Common Data Model, we recommend following these steps:

  1. Create an empty schema.

  2. Execute the script OMOP CDM postgresql ddl.txt to create the tables and fields.

  3. Load your data into the schema.

  4. Execute the script OMOP CDM postgresql indexes required.txt to add the minimum set of indexes and primary keys we recommend.

  5. Execute the script OMOP CDM postgresql constraints.txt to add the constraints (foreign keys).

Note: you could also apply the constraints and/or the indexes before loading the data, but this will slow down the insertion of the data considerably.