4 ms·
This is only true if you have more than one writing connection to the database. But that said, it is still a good idea to not have the database housed on a netw
by warmwaffles 6y ago
This is only true if you have more than one writing connection to the database. But that said, it is still a good idea to not have the database housed on a network attached store.
- bob1029 6y agoOpening connections to SQLite over the network defeats the entire purpose of using this library.
- warmwaffles 6y agoApparently you didn't read the last sentence.
- bob1029 6y agoI definitely did. I was agreeing with you and restating the argument in a more general sense.
- magicalhippo 6y agoThis might sound obvious, but it's not always apparent which applications uses SQLite. I had lots of weird issues with Plex until I found out that uses SQLite, and moved the config directory from a shared NFS directory to a shared iSCSI volume.
- neolog 6y agoYou can keep sqlite on NFS if you disable WAL.
- slenk 6y agoWhat are the disadvantages of disabling WAL? I would love to store a bunch of docker filesystems on NFS but since a lot use SQLite, they all complain.
- neolog 6y agohttps://sqlite.org/wal.html https://sqlite.org/wal.html
- 3np 6y agoIf you write the application yourself (or have easy means to modify it to disable WAL), cool If it’s written by someone else you’d have to maintain a modified fork (if that’s even possible)