[Feature] Use SQLite instead of PostgreSQL for database backend

[Timid Robot Zehta]

Problem

use SQLite instead of PostgreSQL for database backend

Description

Known issues with SQLite do not apply:

• the application features a very small data set that is updated infrequently by a very small group of people
  • if there is concurrency (ex. multiple cron jobs), the default timeout should suffice (the database is small [15M] and all operations are quick)
    • connect — sqlite3 — DB-API 2.0 interface for SQLite databases — Python 3.7.12 documentation (emphasis added):

      The timeout parameter specifies how long the connection should wait for the lock to go away until raising an exception. The default for the timeout parameter is 5.0 (five seconds).

• the application does not use raw queries

Alternatives

Continue to use PostgreSQL

Additional context

• Databases | Django documentation | Django
  • SQLite notes | Databases | Django documentation | Django
• DATABASES | Settings | Django documentation | Django

[Timid Robot Zehta]

⛔ status: discarded

SQLite is not supported by Heroku:

• SQLite on Heroku | Heroku Dev Center

  Why is SQLite a bad fit for running on Heroku?

  Disk backed storage

  [...] If you were to use SQLite on Heroku, you would lose your entire database at least once every 24 hours.

  [...]

  Instead of using SQLite on Heroku you can configure your app to run on Postgres.