For the most part the issues are with the SQLite code. On the SQLite website, you can find
SQLite Over a Network, Caveats and Considerations article for information from the horse's mouth, so to speak.
The other item I've posted a couple of time before is:
Quote:
Not Recommended Over Network Filesystems:
While it is technically possible to place a SQLite database file on a network share, it is strongly discouraged by the developers.
Performance Issues: Latency on most network filesystems significantly degrades performance.
Data Corruption Risk: Network filesystems often have buggy or unreliable file-locking implementations, which can lead to database corruption if multiple processes try to write simultaneously.
Concurrency Limits: SQLite allows unlimited simultaneous readers, but only one writer at a time per database file. This model works well with local file system locks, but is problematic over a network.
|
With the higher speeds and greater reliability of modern WAN connections, it is safer than it was even 5 years ago. OTOH, it is a risk and years of working in IT made me risk adverse.
If you browse through the number of times over the years, that people have not only lost their database but their entire book collection using calibre over a network connection (mostly cloud services but the occasional local NAS box), you might also want to take a look at storing your library locally.