sqlalchemy / sqlalchemy/alembic
Create primary key / unique constraint does not support `postgresql_include` added in sqlalchemy 2.0.41
Open
Nobody has claimed this yet.
op directives
postgresql
use case
- Dominant language
- Python
- Stars
- 4.4k
- Forks
- 375
- PR merge metrics
- No merged PRs in 30d
Description
Describe the use case
When https://github.com/sqlalchemy/sqlalchemy/issues/10665 was implemented alembic was not updated to support these
Databases / Backends / Drivers targeted
postgresql
Have a nice day!
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 reading SQLAlchemy issue 10665 to understand the implemented postgresql_include behavior, then inspect Alembic's primary-key and unique-constraint creation paths. Done means Alembic supports postgresql_include for both constraint types on PostgreSQL, with behavior aligned to SQLAlchemy 2.0.41.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python, sqlalchemy
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100