4 ms·
I did that in 2006. A big win was maintenance, since downloading/uploading a copy of the database was so simple. Eventually I had performance problems when doin
by geon 13y ago
I did that in 2006. A big win was maintenance, since downloading/uploading a copy of the database was so simple. Eventually I had performance problems when doing read-write-read-write stuff, since writing locks the entire db file.
You could argue I shouldn't be doing that, and you may be right. But I just switched back to MySQL, and the problem went away.
- rogerbinns 13y agoSQLite fixed that issue in 2010 with write ahead logging (version 3.7). Writes go to a separate file so there is no impact on readers of the main file. It is a little more complex than that and described at https://www.sqlite.org/wal.html https://www.sqlite.org/wal.html