summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVasu Nori <vnori@google.com>2010-10-04 18:10:51 -0700
committerVasu Nori <vnori@google.com>2010-10-04 18:10:51 -0700
commit060e25bf124c530423c589622c220828a7f35086 (patch)
treeb85c72450b8a2929dabfc125a7582252682f8442
parentf124ce7394595d7c3107e182933119de589d4162 (diff)
downloadframeworks_base-060e25bf124c530423c589622c220828a7f35086.zip
frameworks_base-060e25bf124c530423c589622c220828a7f35086.tar.gz
frameworks_base-060e25bf124c530423c589622c220828a7f35086.tar.bz2
don't print informational messages from sqlite in log
right now, all messages from sqlite are printed in the logfile. if the error code = 0, then sqlite message is just an informational message that usually has no meaning to the developers and ends up confusing the developers. discard such messages Change-Id: I961f1b33a745d5e9b20c85ee8a0071c92c253d96
-rw-r--r--core/jni/android_database_SQLiteDatabase.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/core/jni/android_database_SQLiteDatabase.cpp b/core/jni/android_database_SQLiteDatabase.cpp
index 05e1ff3..1b68ba9 100644
--- a/core/jni/android_database_SQLiteDatabase.cpp
+++ b/core/jni/android_database_SQLiteDatabase.cpp
@@ -77,7 +77,7 @@ static char *createStr(const char *path, short extra) {
static void sqlLogger(void *databaseName, int iErrCode, const char *zMsg) {
// skip printing this message if it is due to certain types of errors
- if (iErrCode == SQLITE_CONSTRAINT) return;
+ if (iErrCode == 0 || iErrCode == SQLITE_CONSTRAINT) return;
LOGI("sqlite returned: error code = %d, msg = %s\n", iErrCode, zMsg);
}