What it is
Asynchronous access to an SQLite database from Python: a query to the database file does not stall the bot while it answers other people.
How we use it
In the birthday bot, the gaming-club loyalty card and the voice transcription bot the whole database is one SQLite file, and aiosqlite reads and writes it without holding up message handling. A backup is a copy of the file.
Where it helps a business
A small bot for a club, a family or one department does not need a separate database server. One SQLite file is enough, and aiosqlite reads and writes it so the bot does not freeze while answering other people.
How we use it
Common problems
- Copying a live database. A backup copy of the file is best taken while the container is stopped; otherwise it may be copied mid-write.
- Time in UTC. The loyalty card stores time in UTC, and this is listed among its limitations.
When you do not need it
If several services, many administrators at once or reports over a long history are involved, we use PostgreSQL or MariaDB.