sqlalchemy / sqlalchemy/alembic
autogen with constraint names that were truncated due to max_identifier_length
Open
Nobody has claimed this yet.
autogenerate - detection
bug
naming convention issues
Tier 1
- Dominant language
- Python
- Stars
- 4.4k
- Forks
- 375
- PR merge metrics
- No merged PRs in 30d
Description
Migrated issue, originally created by Michael Bayer (@zzzeek)
one easy way to work around this is to apply the max_ident rules in autogen on the metadata side. just not sure what unintended consequences this might have.
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 tracing Alembic autogen's handling of constraint names against SQLAlchemy metadata and the max_identifier_length rule. Determine the intended behavior for names truncated by the limit, check for unintended metadata-side effects, and verify the result with focused autogen coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sqlalchemy
- Domain
- database
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100