| 5a05c23f3d6a1a895bf5917aacd8bd9a5302ba00 |
|
12-Jan-2012 |
Jeff Brown <jeffbrown@google.com> |
Clean up database tests a little bit.
Change-Id: Ib05c699bf59187cb51627b5f352c2a15ad2c28bb
/frameworks/base/core/tests/coretests/src/android/database/DatabaseGeneralTest.java
|
| a017edace756956cd4b4789a85316e3681d04a7e |
|
27-Jan-2011 |
Vasu Nori <vnori@google.com> |
bug:3398527 return List insttead of ArrayList from public API
Change-Id: Idbdcb59fe860a9168c9ef6c00eb128b05fce84ff
/frameworks/base/core/tests/coretests/src/android/database/DatabaseGeneralTest.java
|
| fb16cbd9b2e86d6878d4bff820422bc09c8938de |
|
26-Jul-2010 |
Vasu Nori <vnori@google.com> |
add new API in SQLiteStatement to deprecate another.
1. SQLIteStatement.executeUpdateDelete() replaces execute() - and returns the
number of rows changed.
2. let SQLiteDatabase.execSQL() call the above new API - which
means all CRUD statements by execSQL() are stored in prepared statement cache.
3. remove the following from SQLiteDatabase
lastrowId
lastchangecount()
native_execSQL()
Change-Id: I4e93a09dc381f425c3ae6ccc331a7bf227491e22
/frameworks/base/core/tests/coretests/src/android/database/DatabaseGeneralTest.java
|
| 59d60420ba9246eee152852b6a597a0aba7f704d |
|
04-Jul-2010 |
Vasu Nori <vnori@google.com> |
deprecate method returning prepared sql statement id
this method causes sql statement in a SQLiteProgram object to be never
re-compiled. thats not desirable, is it?
there should be no need for this method.
Change-Id: I207fad6415c1e2ef4097ee65a3ff347b5435b994
/frameworks/base/core/tests/coretests/src/android/database/DatabaseGeneralTest.java
|
| 7501010b71d57264a06f82937f5fb29cb9f4b509 |
|
02-Jul-2010 |
Vasu Nori <vnori@google.com> |
some refactoring and multi-threading fixes
Change-Id: I7a0497dc2ed7b1e21471d71532558ef243eb9f73
/frameworks/base/core/tests/coretests/src/android/database/DatabaseGeneralTest.java
|
| d2cecfd3759d6785c5a2ed3f2f35fa1a30f757db |
|
04-Jun-2010 |
Vasu Nori <vnori@google.com> |
fix broken-test
Change-Id: I3d33cda2e4f1ba68843d6a81b8c624ce4af8519f
/frameworks/base/core/tests/coretests/src/android/database/DatabaseGeneralTest.java
|
| 6f37f83a4802a0d411395f3abc5f24a2cfec025d |
|
19-May-2010 |
Vasu Nori <vnori@google.com> |
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
/frameworks/base/core/tests/coretests/src/android/database/DatabaseGeneralTest.java
|
| 85f08f9eaeae6b04c6ce42e5b9dc097ac3e70fc5 |
|
19-May-2010 |
Vasu Nori <vnori@google.com> |
DatabaseCorruptionHandler causes NPE
it is trying to get attachedDb list (by executing a pragma) after closing
the database.
also added unittests.
Change-Id: I7dce665ec7354402cdef6fbe055455f5798e123c
/frameworks/base/core/tests/coretests/src/android/database/DatabaseGeneralTest.java
|
| 7cd51efcbd2d083bf577696591ef1769034f7e2f |
|
13-May-2010 |
Jeff Hamilton <jham@android.com> |
Remove the deprecated cursor methods.
Change-Id: Ie3571fea9f36996c31c327240b11086f8cc487f0
/frameworks/base/core/tests/coretests/src/android/database/DatabaseGeneralTest.java
|
| 9504c70f8862f5ffc55b07bc374e0b18b78a2dc6 |
|
23-Apr-2010 |
Vasu Nori <vnori@google.com> |
fix a bug introduced when prepared-statement cache was made LRU-based
1. when an entry is pushed out of cache, it should be released if it is not
in use by any thread. This didn't have to be done when cache was NOT LRU
because the object either got into the cache while the caller had a reference
to it or it didn't. if it didn't get into cache (because cache is full),
the caller's close() released the object. But in LRU cache, an object
could get pushed out of cache due to LRU policy and if it is NOT in use
by any thread at the time it was pushed out of cache, then it
got GC'ed - which caused warnings to be pronted in the log.
2. also delete some unused methods in SQLiteDatabase.
Change-Id: I7831952647d3a057342bcc8ac186a6a26eb58f33
/frameworks/base/core/tests/coretests/src/android/database/DatabaseGeneralTest.java
|
| 062fc7ce369758d5a26f83f12b50b11cd88e5def |
|
01-Apr-2010 |
Vasu Nori <vnori@google.com> |
allow apps to specify actions to take on database corruption error
let the user specify an interface impl class to specify the actions
to take when db corruption is detected.
this class is specified when the database is opened/created.
Change-Id: I84eb57208c8fedfa7235805b0ec58165efdc1560
/frameworks/base/core/tests/coretests/src/android/database/DatabaseGeneralTest.java
|
| b945639d0c3fa1850c07a2b80f476c8d242a8bde |
|
15-Mar-2010 |
Daisuke Miyakawa <dmiyakawa@google.com> |
Make JNI function for setLocale() call register_localized_collators()
with the current locale, not previous one, every time it is possible.
Add a unit test verifying this fix.
BUG: 2514026
Change-Id: I4dd1b047e1ab4bf399e2c3ebc0304c0cfa3a0928
/frameworks/base/core/tests/coretests/src/android/database/DatabaseGeneralTest.java
|
| d606b4bf2c1a2308b40785860853cfb95a77bf58 |
|
24-Feb-2010 |
Vasu Nori <vnori@google.com> |
in finalize() methods, log warnings if db lock is going to be held.
this is to track bug:2463988 and bug:2457342
/frameworks/base/core/tests/coretests/src/android/database/DatabaseGeneralTest.java
|
| e8de28415b4362824a52c180adf10dd882d12eaf |
|
18-Feb-2010 |
Vasu Nori <vnori@google.com> |
bug fix for 2419869. also included 2 unittests.
bug fix for 2419869 is the following
1. only one object can use the prepared statement object
(SQLiteCompiledSql in SQLIteProgram)
2. if two objects are requesting to use it, then create a new prepared
statement object for exclusive use by the newcomer and let it be
be finalized by the newcomer.
3. add mInUse flag to SQLiteCompiledSql - to be set when SQLiteProgram
requests it and to be released when that SQLiteProgram is done with it
a couple more changes included are
1. unitests to simulate bug # 2419869 (and the fix's repair to it)
2. better logging in SQLiteCloseable when it prints log messages
/frameworks/base/core/tests/coretests/src/android/database/DatabaseGeneralTest.java
|
| 1a44d5dcabc18cd5ef111f732ccff91683a1a093 |
|
13-Jan-2010 |
Neal Nguyen <tommyn@google.com> |
Phase 2 of test cleanup: moving test files from AndroidTests closer to their sources.
Most of these are file moves; a couple notable exceptions are the changes due to the move, and fixing up test code:
- database/DatabaseCursorTest.java
- database/DatabaseStatementTest.java
- net/UriTest.java
/frameworks/base/core/tests/coretests/src/android/database/DatabaseGeneralTest.java
|