diff options
author | Vasu Nori <vnori@google.com> | 2010-01-15 10:44:57 -0800 |
---|---|---|
committer | Vasu Nori <vnori@google.com> | 2010-01-15 10:49:06 -0800 |
commit | bee5b9d7cb9071b617810b8018e69b6815478e46 (patch) | |
tree | f2581027bd60986520cfd15c29ba88f713a1a7a1 | |
parent | c5dfa70410121c63079ecd7e4945d774562c8998 (diff) | |
download | frameworks_base-bee5b9d7cb9071b617810b8018e69b6815478e46.zip frameworks_base-bee5b9d7cb9071b617810b8018e69b6815478e46.tar.gz frameworks_base-bee5b9d7cb9071b617810b8018e69b6815478e46.tar.bz2 |
Change Log.wtf() call to Log.w()
messages from Log.wtf() sound pretty bad and engineers seem to think
something terrible has gone wrong.
-rw-r--r-- | core/java/android/database/sqlite/SQLiteDatabase.java | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/core/java/android/database/sqlite/SQLiteDatabase.java b/core/java/android/database/sqlite/SQLiteDatabase.java index b59030d..fb44a62 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<String> keySet = mCompiledQueries.keySet(); for (String s : keySet) { |