sqlalchemy / sqlalchemy/sqlalchemy
add official API to have naming conventions work for alternate constraint types
Open
Nobody has claimed this yet.
naming conventions
schema
- Dominant language
- Python
- Stars
- 12.2k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
Using them is poorly tested and the use case seems quite limited.
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 does not name files, tests, or an entry point. Start by locating SQLAlchemy's naming-convention handling and the existing support for constraint types, then review how alternate constraint types are currently tested. Done means an agreed official API and coverage for the supported alternate types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100