From 8a397486548beed1ad505a7e56211ccf49d50b5d Mon Sep 17 00:00:00 2001 From: Markus Goetz Date: Wed, 13 May 2015 14:57:14 +0200 Subject: [PATCH] SyncJournalDB: Don't use NULL value Olivier says we should try to not be the same as the possible value for not existing entries. --- src/libsync/syncjournaldb.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/libsync/syncjournaldb.cpp b/src/libsync/syncjournaldb.cpp index 9c35269c3..ce2bf036f 100644 --- a/src/libsync/syncjournaldb.cpp +++ b/src/libsync/syncjournaldb.cpp @@ -333,7 +333,7 @@ bool SyncJournalDb::checkConnect() if (forceRemoteDiscovery) { qDebug() << "Forcing remote re-discovery by deleting folder Etags"; SqlQuery deleteRemoteFolderEtagsQuery(_db); - deleteRemoteFolderEtagsQuery.prepare("UPDATE metadata SET md5=NULL WHERE type=2;"); + deleteRemoteFolderEtagsQuery.prepare("UPDATE metadata SET md5='_invalid_' WHERE type=2;"); if( !deleteRemoteFolderEtagsQuery.exec() ) { qDebug() << "ERROR: Query failed" << deleteRemoteFolderEtagsQuery.error(); } else { -- 2.30.2