sqlalchemy / sqlalchemy/alembic
Support PostgreSQL partitioned tables
Open
Nobody has claimed this yet.
autogenerate - detection
feature
postgresql
- Dominant language
- Python
- Stars
- 4.4k
- Forks
- 375
- PR merge metrics
- No merged PRs in 30d
Description
I use PostgreSQL and if table is partitioned then autogeneration repeats creation of this table when it's already exist. Also Alembic generates deletion of all partitions of partitioned table.
Is it bug or there is some way to get around it?
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 files or tests are named. Start by reproducing autogeneration with a PostgreSQL partitioned table and inspect the generated migration. Done means an existing partitioned table is not recreated and its partitions are not scheduled for deletion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100