4 ms·
If your use case involves a requirement for master/slave replication, SQLite might be a little too lightweight for your needs.
by aaronem 12y ago
If your use case involves a requirement for master/slave replication, SQLite might be a little too lightweight for your needs.
- jmtulloss 12y agoI totally agree, I just thought it was odd that the article didn't mention it. There was a section on when SQLite might not be appropriate, but it never mentions this. Easily avoiding data loss is a huge feature for a db that's going to have any amount of production data, so if you're proposing that people use SQLite for production workloads, this should be acknowledged.