6f37f83a4802a0d411395f3abc5f24a2cfec025d - platform_frameworks_base

commit	6f37f83a4802a0d411395f3abc5f24a2cfec025d	[log] [tgz]
author	Vasu Nori <vnori@google.com>	Wed May 19 11:53:25 2010 -0700
committer	Vasu Nori <vnori@google.com>	Thu May 20 12:35:17 2010 -0700
tree	4486642129bc5f456fa410c0bc12fef8bf12cbc3
parent	6b72dbe9c306d6c70ce06cebbff2821f3b5b8e8f [diff]

close() on anything other than database shouldn't acquire db lock.

bug:2683001
implmentation details:
 1.close() on any sql statement is should simply queued up for finalization
    to be performed later. caller doesn't acquire database lock.
 2. the only effect of NOT close immediately is non-release of some memory.
 3. all such queued-up-finalizations are performed whenever there is
    another execute() of some sql statement on that database from ANY
    thread in the process.
 4. database close() automatically releases all unfinalized statements
    before closing the database.

Change-Id: If4c9c7fde6b8945a41abc6c8b992aa8c69854512

core/java/android/database/sqlite/SQLiteCompiledSql.java[diff]
core/java/android/database/sqlite/SQLiteDatabase.java[diff]
core/java/android/database/sqlite/SQLiteDirectCursorDriver.java[diff]
core/java/android/database/sqlite/SQLiteProgram.java[diff]
core/java/android/database/sqlite/SQLiteStatement.java[diff]
core/jni/android_database_SQLiteCompiledSql.cpp[diff]
core/jni/android_database_SQLiteDatabase.cpp[diff]
core/tests/coretests/src/android/database/DatabaseGeneralTest.java[diff]

8 files changed

tree: 4486642129bc5f456fa410c0bc12fef8bf12cbc3