From a63e4e2322e8d4644eb9d0139ce9671c638aa8de Mon Sep 17 00:00:00 2001
From: Stephan Tietz <1504437+stietz@users.noreply.github.com>
Date: Sun, 17 Nov 2019 13:16:11 +0000
Subject: [PATCH] Updated Running without WAL enabled (markdown)

---
 Running-without-WAL-enabled.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Running-without-WAL-enabled.md b/Running-without-WAL-enabled.md
index 49757fc..06bd8b6 100644
--- a/Running-without-WAL-enabled.md
+++ b/Running-without-WAL-enabled.md
@@ -6,6 +6,7 @@ Generally speaking unless you're absolutely sure, that you need to turn WAL off,
 
 * Some filesystems don't support WAL - this is especially true for network filesystems. If you're using such filesystem, the service will fail to start with `Failed to turn on WAL` error message.
 * The database requires sqlite version `3.7.0` or newer, so if you for any reason (for example backups) require to access the DB directly with some other tool that cannot be updated, you might need to disable WAL.
+* You are using the MySQL backend.
 * One of the [disadvantages described here](https://sqlite.org/wal.html#advantages) affects you
 
 ## How to turn WAL off