
Using the SQLite3 engine does allow me to in the future do horrible things like having blobs in the data, which means being able to store photos (without encoding).Īt least with the per-job file system, it's exceptionally low risk of two people writing to the file concurrently. At least with SQLite3 files the overheads are quite low (not that space is a major issue at these scales). In order to minimise corruption risks from access contention or race conditions, I'll likely make it so that there is an index database and each job will be its own separate database. By -default- I'd just utilise that folder but I can give people the option to set it to another folder of choice, of which could be on a shared folder/drive. Depending on the system, they'd normally be stored in the user-data-dir (linux,macOS and Windows all have their own idea of what's best there).
