Change foreign key constraints to be deferrable in PostgreSQL DDL (and possibly others?)
Open
Nobody has claimed this yet.
Enhancement
- Dominant language
- HTML
- Stars
- 1.1k
- Forks
- 508
- Avg merge
- 1h 30m
- Merged PRs (30d)
- 3
Description
Would it make sense to introduce "DEFERRABLE" keyword when creating foreign key constraints in these tables? It simplifies process of actually populating tables from Athena downloads or making local changes, without having to drop and re-create constraints.
Links:
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 with inst/ddl/5.4/postgresql/OMOPCDM_postgresql_5.4_constraints.sql and the linked PostgreSQL SET CONSTRAINTS documentation. Determine whether the request applies only to PostgreSQL or to other DDL variants as well; done means the agreed foreign-key constraint definitions are updated consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100