>From time to time, we run into bugs with the SQLite dialect in SQLAlchemy and
>close the bugs as "wont-fix" because we don't want to be in the business of
>fixing such bug. We deem SQLite as a "non-serious" database that no one [in
>his/her right mind] would run in his/her staging, qa, or production
>environments. However, we rely on the SequentialExecutor and one the SQLite DB
>for our tests.
What should we do with SQLite? Should we lift up the hood and fix it for our
needs or find either a different ORM or a different option for DB backend?
Example of bugs we encounter and close as won't fix : 1. Deleting a task
instance : https://github.com/airbnb/airflow/issues/9552. Weird pickle issue :
https://issues.apache.org/jira/browse/AIRFLOW-46
