[GitHub] [airflow] mattinbits commented on issue #21171: Airflow schedules tasks in wrong timezone with an MSSQL Metadata DB on a non-UTC server

2023-01-23 Thread via GitHub
mattinbits commented on issue #21171: URL: https://github.com/apache/airflow/issues/21171#issuecomment-1400287367 > > @potiuk As an initial fix for our internal system, I replaced `func.now()` with `func.GETDATE()` in an internal fork which is enough to fix it for SQL Server. This is not

[GitHub] [airflow] mattinbits commented on issue #21171: Airflow schedules tasks in wrong timezone with an MSSQL Metadata DB on a non-UTC server

2023-01-23 Thread via GitHub
mattinbits commented on issue #21171: URL: https://github.com/apache/airflow/issues/21171#issuecomment-147539 As someone who has been running Airflow on MSSQL in production for several years, I tend to agree that explicitly removing support would be better. We're planning to move away

[GitHub] [airflow] mattinbits commented on issue #21171: Airflow schedules tasks in wrong timezone with an MSSQL Metadata DB on a non-UTC server

2022-04-26 Thread GitBox
mattinbits commented on issue #21171: URL: https://github.com/apache/airflow/issues/21171#issuecomment-1109871339 @uranusjr is it the case then that you prefer a solution that continues to rely on the database to get the current timestamp, rather than adopt `timezone.utcnow()` and