`manager.has_constraint` for migrations
Open
Nobody has claimed this yet.
Area:migration
Category:enhancement
- Dominant language
- Rust
- Stars
- 9.9k
- Forks
- 735
- Avg merge
- 6h 36m
- Merged PRs (30d)
- 8
Description
Motivation
The SchemaManager has convenience methods like has_table and has_column while writing migrations. I propose a has_constraint method.
Proposed Solutions
It will return true if an constraint exists for a given table.
Current Workarounds
Execute the query manually.
If accepted I would like to make a PR.
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
Start by locating SchemaManager and its existing has_table and has_column methods, then review how migrations query supported database backends. Clarify which constraint types and database behaviors the method must cover before defining the API. Done means the behavior is specified and verified consistently across the relevant migration backends.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100