3 ms·
>when you backup your machine, do you really treat each sqlite specially? Yes, but only for servers where the database is being used. On my desktop if the data
by charcircuit 3y ago
>when you backup your machine, do you really treat each sqlite specially?
Yes, but only for servers where the database is being used. On my desktop if the database isn't being used it is safe to copy so I don't worry about it. Backing up a git repo while git is writing to the repo isn't safe either.
>or, you know, downloading database file and forgetting to grab journal at the same time
You should not be downloading an actively used sqlite database anyways. If you backup the sqlite database before downloading it there won't be a journal file.
>did you ever hardlink or bind-mounted a database file? prepare for corruption...
You just have to link both the database and WAL file. This is somewhat challenging since the WAL file will be deleted by default if all processes close the database. It's better to link or mount the directory that contains the database file. If you link only some of the files from .git, then git won't work properly either.