From fb03c87305c8df1bdbd7467179c21950ce2744e0 Mon Sep 17 00:00:00 2001
From: Dan Stillman <dstillman@zotero.org>
Date: Sat, 16 Nov 2013 15:45:23 -0500
Subject: [PATCH] Disable full-text purging, for now

This isn't technically any slower than before, but if people were using
multiple computers, they might not have had their entire full-text index
on a single computer before full-text syncing.
---
 chrome/content/zotero/xpcom/zotero.js | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/chrome/content/zotero/xpcom/zotero.js b/chrome/content/zotero/xpcom/zotero.js
index 0a2fd759e3..8b44696e2f 100644
--- a/chrome/content/zotero/xpcom/zotero.js
+++ b/chrome/content/zotero/xpcom/zotero.js
@@ -1965,7 +1965,8 @@ Components.utils.import("resource://gre/modules/Services.jsm");
 	this.purgeDataObjects = function (skipStoragePurge) {
 		Zotero.Creators.purge();
 		Zotero.Tags.purge();
-		Zotero.Fulltext.purgeUnusedWords();
+		// TEMP: Disabled until we have async DB (and maybe SQLite FTS)
+		//Zotero.Fulltext.purgeUnusedWords();
 		Zotero.Items.purge();
 		// DEBUG: this might not need to be permanent
 		Zotero.Relations.purge();