Skip to content

Add op.run_async to allow running async function from upgrade/downgrade when using an async engine #1231

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
CaselIT opened this issue Apr 28, 2023 · 1 comment
Closed

Add op.run_async to allow running async function from upgrade/downgrade when using an async engine #1231

CaselIT opened this issue Apr 28, 2023 · 1 comment
Labels
asyncio use case not quite a feature and not quite a bug, something we just didn't think of
Milestone
1.11

Comments

@CaselIT
Copy link
Member

CaselIT commented Apr 28, 2023

The function that's called should probably receive an async connection as the fist argument

Mentioned in #1229
@CaselIT CaselIT added use case not quite a feature and not quite a bug, something we just didn't think of asyncio labels Apr 28, 2023
@sqla-tester
Copy link
Collaborator

Federico Caselli has proposed a fix for this issue in the main branch:

Added op.run_async. https://gerrit.sqlalchemy.org/c/sqlalchemy/alembic/+/4594

@CaselIT CaselIT added this to the 1.11 milestone May 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
asyncio use case not quite a feature and not quite a bug, something we just didn't think of
Projects
None yet
Milestone
1.11
Development

No branches or pull requests
2 participants
@sqla-tester @CaselIT