Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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.

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

Skip autogenerate in multiple database #1250

Closed
0del opened this issue May 25, 2023 · 1 comment
Closed

Skip autogenerate in multiple database #1250

0del opened this issue May 25, 2023 · 1 comment
Labels
use case not quite a feature and not quite a bug, something we just didn't think of

Comments

@0del
Copy link

0del commented May 25, 2023

Describe the use case

I set up Alembic with multiple databases, including PostgreSQL and ClickHouse. I want Alembic to autogenerate with the PostgreSQL database, but skip autogeneration for the ClickHouse.

Databases / Backends / Drivers targeted

Example Use

With ClickHouse: I want to use a raw query in database migration because my database is very difficult.

Additional context

@0del 0del added requires triage New issue that requires categorization use case not quite a feature and not quite a bug, something we just didn't think of labels May 25, 2023
@CaselIT CaselIT removed the requires triage New issue that requires categorization label May 25, 2023
@CaselIT
Copy link
Member

CaselIT commented May 25, 2023

Hi,

Can't you just configure alembic to only use the postgresql engine?

@sqlalchemy sqlalchemy locked and limited conversation to collaborators May 25, 2023
@CaselIT CaselIT converted this issue into discussion #1252 May 25, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
use case not quite a feature and not quite a bug, something we just didn't think of
Projects
None yet
Development

No branches or pull requests

2 participants