Skip autogenerate for an engine in multiple database

[9bany]

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

• I used clickhouse-sqlalchemy plugin but it is not compatible with Alembic and does not strongly support ClickHouse.
• clickhouse-sqlalchemy raised a bug when I tried to use it with alembic. link to -> Bug: _reflect_table() takes 2 positional arguments but 3 were given xzkostyan/clickhouse-sqlalchemy#250
  Have a nice day!

[CaselIT]

Hi,

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

[9bany]

I can't @CaselIT

[CaselIT]

I'm not sure what's the issue in doing this is. If you don't plan to use alembic for a db I can't see the point of making alembic run on that db.

In any case you may be able to filter what autogenerate looks as by using the options documented here https://alembic.sqlalchemy.org/en/latest/autogenerate.html#controlling-what-to-be-autogenerated

[9bany]

I applied to create an alembic.ini file for each database engine that can work, but I hope my case can work with multiple database templates in Alembic, and I can configure it correctly with those.
Thanks for your support, @CaselIT