From 27f7c8d09ab72558e03d7f6bac843b1d0a725936 Mon Sep 17 00:00:00 2001
From: avar <avar@web>
Date: Fri, 16 Jun 2017 20:37:48 +0000
Subject: [PATCH] Added a comment

---
 .../comment_3_079359513b6b9fcf0030f49df0eaf64d._comment   | 8 ++++++++
 1 file changed, 8 insertions(+)
 create mode 100644 doc/forum/Problem_with_corrupt_SQLite_DB/comment_3_079359513b6b9fcf0030f49df0eaf64d._comment

diff --git a/doc/forum/Problem_with_corrupt_SQLite_DB/comment_3_079359513b6b9fcf0030f49df0eaf64d._comment b/doc/forum/Problem_with_corrupt_SQLite_DB/comment_3_079359513b6b9fcf0030f49df0eaf64d._comment
new file mode 100644
index 0000000000..1bc48c8586
--- /dev/null
+++ b/doc/forum/Problem_with_corrupt_SQLite_DB/comment_3_079359513b6b9fcf0030f49df0eaf64d._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="avar"
+ avatar="http://cdn.libravatar.org/avatar/57332d67a86eb51e06bf78d2baf42c3c"
+ subject="comment 3"
+ date="2017-06-16T20:37:47Z"
+ content="""
+What about if you are in v6 mode? I just read the wiki about that version upgrade, sounds exciting, but I got this with <v6 and I'm definitely not switching over if some sqlite error can hose my entire checkout. How do you actually recover from this when sqlite is a hard dependency?
+"""]]