Created attachment 102208 [details] reduce logging with internal mysql Every second the following is printed to the console when running with internal mysql backend: digikam.databaseserver: Waiting 1 seconds... This pollutes stdout a lot and makes it difficult to track important messages. This patch reduces this messages gradually to one message per minute.
Increasing the wait time is not good. DigiKam now needs 60 seconds in the worst case until it finishes completely. Maik
Typically, "digikam.databaseserver: Waiting 1 seconds..." is wrapped by qCDebug(namespace) macro, where namepace is a debug space ID which can be disable at run time. But for the moment, i don't find a simpler way to do it, as we can do with 4.x release through kdebugdialog (which of course do not work with 5.x now). http://doc.qt.io/qt-5/qloggingcategory.html Gilles Caulier
Git commit 48d3f2c983864d4487c4668442ff105e8610c571 by Maik Qualmann. Committed on 13/11/2016 at 20:28. Pushed by mqualmann into branch 'master'. print running time message all 30 seconds from internal MySQL server FIXED-IN: 5.4.0 M +2 -1 NEWS M +11 -2 libs/database/server/databaseserver.cpp http://commits.kde.org/digikam/48d3f2c983864d4487c4668442ff105e8610c571