Field `cohort_definition_id` in table `cohort_definition` should be a primary key.
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.1k
- Forks
- 508
- Avg merge
- 1h 30m
- Merged PRs (30d)
- 3
Description
The field cohort_definition_id in table cohort_definition should be a primary key. The issue is present with version 5.3, and 5.4 (see below), and version 6.0 might introduce another issue (see further below).
5.3
5.4
6.0
Version 6.0 indicates that cohort_definition_id is a foreign key from the field/column cohort_definition_id in table table cohort (where it is not a primary key). Should it be the other way around (field/column cohort_definition_id in table table cohort is a foreign key from cohort_definition.cohort_definition_id?
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 inspecting the referenced rows in inst/csv/OMOP_CDMv5.3_Field_Level.csv, OMOP_CDMv5.4_Field_Level.csv, and OMOP_CDMv6.0_Field_Level.csv, then compare the cohort_definition and cohort key definitions. Done means the primary-key and foreign-key metadata consistently represents the relationship described in the issue across the affected CDM versions.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100