diff options
| author |  edward <edward@web> | 2015-02-19 15:30:15 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2015-02-19 15:30:15 +0000 |
| commit | 20d8da9dbb339ea51edf6363c3fe824e28fd05ed (patch) | |
| tree | fca9e3adf1dd6503a2b5d2adf99cbabd1cf787bf | |
| parent | 8c7e61fba9b32932a1f58f28437e0bce03be7c7b (diff) | |
correct typo: datbase -> database
| -rw-r--r-- | doc/devblog/day_255__sqlite_concurrent_writers_problem.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/devblog/day_255__sqlite_concurrent_writers_problem.mdwn b/doc/devblog/day_255__sqlite_concurrent_writers_problem.mdwn index 779f3f7fd..05b431a4d 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 |