Vasu Nori f3cf8a4da8 when corruption occurs, log a warning before closing db
and database.close() should NOT set mPath to null.

a few other minor changes included in this CL
1. if it is memory database, no need to delete any file
2. if 2 threads are sharing the same connection, and if corruption occurs
on it, one thread closes the db and deletes db - while the other
thread is still using it. this can cause SQLITE_MISUSE error.
to prevent this, every method in SQLiteDatabse should make sure
db is open before exec'ing sql statements. bug:2531172

Change-Id: I4cb5ab8539f46d7f8b26c3f830d799adf46444b6
2010-03-23 15:52:02 -07:00
2010-03-23 11:37:38 -07:00
2010-03-23 11:51:11 -04:00
2010-03-10 22:11:50 -08:00
2010-03-16 09:59:06 -07:00
2010-03-22 15:55:38 -07:00
2010-03-18 14:14:52 -07:00
2010-03-08 18:11:37 -08:00
Description
No description provided
21 GiB
Languages
Java 73.7%
Kotlin 14%
PowerBuilder 5.8%
C++ 5.2%
AIDL 1%