From bee5b9d7cb9071b617810b8018e69b6815478e46 Mon Sep 17 00:00:00 2001 From: Vasu Nori Date: Fri, 15 Jan 2010 10:44:57 -0800 Subject: [PATCH] Change Log.wtf() call to Log.w() messages from Log.wtf() sound pretty bad and engineers seem to think something terrible has gone wrong. --- core/java/android/database/sqlite/SQLiteDatabase.java | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/core/java/android/database/sqlite/SQLiteDatabase.java b/core/java/android/database/sqlite/SQLiteDatabase.java index b59030d85a77e..fb44a629cd110 100644 --- a/core/java/android/database/sqlite/SQLiteDatabase.java +++ b/core/java/android/database/sqlite/SQLiteDatabase.java @@ -1873,8 +1873,8 @@ public class SQLiteDatabase extends SQLiteClosable { * JNI method. If entire cache is wiped out, it could cause a big GC activity * just because a (rogue) process is using the cache incorrectly. */ - Log.wtf(TAG, "Too many sql statements in database cache. Make sure your sql " + - "statements are using prepared-sql-statement syntax with '?' for" + + Log.w(TAG, "Too many sql statements in database cache. Make sure your sql " + + "statements are using prepared-sql-statement syntax with '?' for " + "bindargs, instead of using actual values"); Set keySet = mCompiledQueries.keySet(); for (String s : keySet) {