dstandish commented on PR #22921: URL: https://github.com/apache/airflow/pull/22921#issuecomment-1095525973
> Do we really need to know it that precisely? Can't we use the `VERSION_REVISION_MAP`and walk the migrations history via alembic api? > > Or could we just "duck-type" the database and check what is or isn't present and make decisions based on that. > > (I'm not a huge fan of having to have a whole load of constants in the code that get updated by hooks) I think the duck typing approach is messy and I'd rather just be precise about it. But, we can look it up when running the upgrade command, that is fine -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
