dmeibusch commented on issue #16344: URL: https://github.com/apache/airflow/issues/16344#issuecomment-872644175
I'm not sure that is it possible. The table drop/recreate is at the table level - it would be an optimisation (?) for alembic to determine that within a table alter operation that there is a column rename only that could be done directly without recreating the table. Airflow could detect the variant (and sqlite version) and run the `alter column` directly - one possibility. I didn't understand all the ramifications of the drop/recreate process, but I think with sqlite that alembic struggles if the constraints are unnamed - which I think is the default - to drop/recreate constraints. So, maybe another approach is checking whether Airflow is naming all its constraints. This might be worthwhile for supporting any future migrations with sqlite databases. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
