pgadmin-org / pgadmin-org/pgadmin4
Allow NOT NULL constraints to be added as NOT VALID
Open
Nobody has claimed this yet.
Feature
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 891
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 8
Description
PG 18 and above
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 only specifies support for PostgreSQL 18 and above and does not name files, tests, or an entry point. Start by locating pgAdmin's NOT NULL constraint creation flow and reviewing PostgreSQL 18's NOT VALID behavior; done means the relevant constraint workflow supports this option with coverage for supported and unsupported PostgreSQL versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100