sqlalchemy / sqlalchemy/alembic
generalized "recreate foreign key" / "recreate constraint" / "drop constraint if needed" types of directives + autogenerate?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.4k
- Forks
- 375
- PR merge metrics
- No merged PRs in 30d
Description
Migrated issue, originally created by Stéphane Klein (@harobed)
With MSSql, drop_column have some specific options https://github.com/zzzeek/alembic/blob/master/alembic/operations.py#L504 like : "mssql_drop_foreign_key".
I suggest to append specifics options for Mysql :
- "mysql_drop_contraints"
- "mysql_drop_foreign_key"
What do you think about this suggest ?
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 in alembic/operations.py around the existing MSSQL-specific drop_column options referenced in the issue. Read the comment discussion before defining the scope, since the request covers generalized constraint directives and autogenerate behavior. Done requires an agreed design and implementation for the supported database cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql, python, sql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100