pgadmin-org / pgadmin-org/pgadmin4
ENFORCED / NOT ENFORCED syntax added for Foreign Key and CHECK constraints
Open
Nobody has claimed this yet.
Feature
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 891
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 8
Description
This issue has no description.
Contributor guide
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
The issue body names no files, tests, or entry points. Start by locating pgAdmin's PostgreSQL handling for foreign-key and CHECK constraints, then identify where ENFORCED / NOT ENFORCED syntax is represented. Done means the requested syntax is supported consistently for both constraint types and verified with relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100