[ownedbycats]

Originally Posted by sile2001

Madness. To think it normal that a somewhat widely-used application in 2023 doesn't support a mechanism that has been in Windows since 1995, Linux since the mid-to-late 90's (at least), and OSX since 2002. Got it.

Network filesystems are simply too limited for the types of thing Calibre does with file locking and the such. SQLite especially:

https://www.sqlite.org/whentouse.html

SQLite will work over a network filesystem, but because of the latency associated with most network filesystems, performance will not be great. Also, file locking logic is buggy in many network filesystem implementations (on both Unix and Windows). If file locking does not work correctly, two or more clients might try to modify the same part of the same database at the same time, resulting in corruption. Because this problem results from bugs in the underlying filesystem implementation, there is nothing SQLite can do to prevent it.

https://www.sqlite.org/useovernet.html

This simple, "remote database" approach is usually not the best way to use a single SQLite database from multiple systems, (even if it appears to "work"), as it often leads to various kinds of trouble and grief.

https://stackoverflow.com/questions/...-network-share

My experience of file based databases (i.e. those without a database server process), which goes back over twenty years, is that if you try to share them, they will inevitably eventually get corrupted. I'd strongly suggest you look at MySQL again.

And please note, I am not picking on SQLite - I use it myself, just not as a shared database.