sqlalchemy / sqlalchemy/alembic
implement detection of collation changes on a column
Open
Nobody has claimed this yet.
autogenerate - detection
use case
- Dominant language
- Python
- Stars
- 4.4k
- Forks
- 375
- PR merge metrics
- No merged PRs in 30d
Description
I have found the same problem as described in #475 ,
when you change for example String field with adding collation parameter to it - alembic does not see this change on autogenerate
Versions.
- OS: MS Windows 10
- Python: 3.9.10
- Database: PostgreSQL 12
- alembic 1.7.7
- SQLAlchemy 1.4.35
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
No file, test, or entry point is named in the issue. Start by reproducing autogenerate with a PostgreSQL String column whose collation changes, using the versions reported here and the related behavior in #475 as context; done means the change is detected during autogenerate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python, sqlalchemy
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100