SyncJournalDB: Don't use NULL value

Olivier says we should try to not be the same as the possible value
for not existing entries.

diff --git a/src/libsync/syncjournaldb.cpp b/src/libsync/syncjournaldb.cpp
index 9c35269c38f7f0177dd6f90c162ea5f888b12a5f..ce2bf036f100d5165e6fc287aad49f3e31c1d4d9 100644 (file)
--- 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 {