ephraimbuddy commented on PR #49002:
URL: https://github.com/apache/airflow/pull/49002#issuecomment-2863601841

   So, the bug I fixed is unrelated. I think I understand what's happening. The 
DB is 
[initialized](https://github.com/apache/airflow/blob/c7afcfc568b5f1bfc5c5be5b780ddc0f8320f976/devel-common/src/tests_common/test_utils/db.py#L94-L97)
 from the ORM, and we try to run the file migration, too, by running downgrade 
and upgrade commands. In the end, the new field you added is already in the DB. 
When the `alembic check` command is run, the database already has the new 
field, and therefore, it's not detected. 
   
   In airflow 2, we could easily detect this new field because our tests 
initializes the database from the migration files instead of the ORM. 


-- 
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]

Reply via email to