History log of /frameworks/base/core/java/android/database/sqlite/DatabaseObjectNotClosedException.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
20f549fd2f40db524242c9038d7d63356adf95fc 15-Apr-2010 Vasu Nori <vnori@google.com> several minor bugs and things listed below

bug:1648729
print warning if a requery is attemped on main thread
bug:2459293
browser death because of NoSuchElementException. don't use iterator
to march thru the ArrayList. use old style for() loop.
bug:1609474
don't allow downgrades of databases
other stuff
use LRUcache to maintain statement-cache in SQLiteDatabase
Change-Id: I3a42022162f4dfcc75f7d0cfcad8f20f1d193249
/frameworks/base/core/java/android/database/sqlite/DatabaseObjectNotClosedException.java
4da24f428f7f45dad677c83e3e1085560e3c5f81 03-Mar-2010 Vasu Nori <vnori@google.com> hide the newly created DatabaseObjectNotClosedException class from sdk
/frameworks/base/core/java/android/database/sqlite/DatabaseObjectNotClosedException.java
08b448ea39e9fabfc5212ae6f7226eba4385d189 03-Mar-2010 Vasu Nori <vnori@google.com> in finalizer warnings, use a better exception - NOT Exception()

finalizer warnings should use a more descriptive exception instead of
Exception() so it is clearer to the developers as to why this
warning is output.
/frameworks/base/core/java/android/database/sqlite/DatabaseObjectNotClosedException.java