Did you regenerate your migration script after adding the hooks?
I would start by putting some print statements in the include_name hook to
see how it is being called. You should see it called for every object in
the database. You can then decide which names to return True for, and which
ones to
Thank you Simon for your response. yes i am using autogenerate feature. i
tried with include_object and include_name hooks. but it won't work for me.
after adding hook also alembic touches to existing tables..
if you send the code snipet for env.py file.. that will really help me..
Thank you.
If I understand correctly, you used Alembic's "autogenerate" feature to
create your migration script. This feature compares the table definitions
in your application with the table definitions in the database and then
generates a script to alter the database to match your application.
You can
I am working on fastapi, in which i have created models and i am inteded to
create the table in sql server database, however when i am runing my first
migration, alembic detected removal of existing table which are not belongs
to my work. Can somebody help how i can create my tables and avoid
