From 89b97bcdbcd277872f6fef0e44d98174fd1c04a7 Mon Sep 17 00:00:00 2001 From: edward Date: Thu, 19 Feb 2015 15:30:15 +0000 Subject: [PATCH] correct typo: datbase -> database --- doc/devblog/day_255__sqlite_concurrent_writers_problem.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/devblog/day_255__sqlite_concurrent_writers_problem.mdwn b/doc/devblog/day_255__sqlite_concurrent_writers_problem.mdwn index 779f3f7fd7..05b431a4dc 100644 --- a/doc/devblog/day_255__sqlite_concurrent_writers_problem.mdwn +++ b/doc/devblog/day_255__sqlite_concurrent_writers_problem.mdwn @@ -4,7 +4,7 @@ multiple concurrent fsck processes. The first problem was that having `fsck --incremental` running and starting a new `fsck --incremental` caused it to crash. And with good reason, since starting a new incremental fsck deletes the old database, the old process -was left writing to a datbase that had been deleted and recreated out from +was left writing to a database that had been deleted and recreated out from underneath it. Fixed with some locking. Next problem is harder. Sqlite doesn't support multiple concurrent writers