www

commit 2468ad5dfcf3716b5d5e476f7a21dd96aae113db
parent 38be4790a1dfcd8d0bb22e01fb9087f9c9e370a4
Author: Dan Stillman <dstillman@zotero.org>
Date:   Mon, 29 Dec 2008 10:31:29 +0000

Fix a potential upgrade error due to the initial 1.5 migration step not adding a UNIQUE index to `key` in syncDeleteLog


Diffstat:
M
chrome/content/zotero/xpcom/schema.js
 | 
2
+-

1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/chrome/content/zotero/xpcom/schema.js b/chrome/content/zotero/xpcom/schema.js
@@ -2150,7 +2150,7 @@ Zotero.Schema = new function(){
 					Zotero.DB.query("DROP INDEX syncDeleteLog_timestamp");
 					Zotero.DB.query("CREATE TABLE syncDeleteLog (\n    syncObjectTypeID INT NOT NULL,\n    key TEXT NOT NULL UNIQUE,\n    timestamp INT NOT NULL,\n    FOREIGN KEY (syncObjectTypeID) REFERENCES syncObjectTypes(syncObjectTypeID)\n);");
 					Zotero.DB.query("CREATE INDEX syncDeleteLog_timestamp ON syncDeleteLog(timestamp);");
-					Zotero.DB.query("INSERT INTO syncDeleteLog SELECT syncObjectTypeID, key, timestamp FROM syncDeleteLogOld");
+					Zotero.DB.query("INSERT IGNORE INTO syncDeleteLog SELECT syncObjectTypeID, key, timestamp FROM syncDeleteLogOld ORDER BY timestamp DESC");
 					Zotero.DB.query("DROP TABLE syncDeleteLogOld");
 				}
 			}