| 12669b6c8073defcfae369e9f7b6f879b1ac218e |
|
18-Feb-2011 |
Vasu Nori <vnori@google.com> |
bring back sqlite WAL tests now that the feature is in.
Change-Id: I92103915845b7cf3f41f95e909051b6669c63ec4
/frameworks/base/core/tests/coretests/src/android/database/sqlite/SQLiteCursorTest.java
|
| e7dea4ec2479002f5ee15bc6fc98d8c8acd123a6 |
|
10-Feb-2011 |
Vasu Nori <vnori@google.com> |
bug:3443154 fix database tests after disabling sqlite wal
sqlite wal is disabled in Change-Id: I283ad26ba7e1793772a372aa8e24df0cb96ce2ef
Change-Id: I2b370c65390a9293e4a82f650c9cee8023b861d7
/frameworks/base/core/tests/coretests/src/android/database/sqlite/SQLiteCursorTest.java
|
| c2ce721fcf684189b7251a5ecbf386426490d68e |
|
06-Oct-2010 |
Vasu Nori <vnori@google.com> |
fix broken build
Change-Id: Ic00e8b98780d48928e05ee27f855e8211fb1ec47
/frameworks/base/core/tests/coretests/src/android/database/sqlite/SQLiteCursorTest.java
|
| 790762ca8f4fa458b87f75e7e8cde965c9efe3e5 |
|
06-Oct-2010 |
Vasu Nori <vnori@google.com> |
annotate some tests large - just in case they take longer. bug:3066136
Change-Id: I89ab0454f592748f971b678a3ae23724eb6fc2e5
/frameworks/base/core/tests/coretests/src/android/database/sqlite/SQLiteCursorTest.java
|
| b18f27dbf43ee9028a11cafbca23d3fa318e278b |
|
13-Aug-2010 |
Vasu Nori <vnori@google.com> |
Return count of rows in a resultset only once (when startPos = 0)
If a query returns 100 rows and say only 10 rows fit in 1MB, then client
receiving the cursor from the ContentProvider needs to paginate.
ContentProvider returns count of total data everytime it returns a page
(= 1MB) of data to the client.
Returning total count causes reading (and skipping unwanted) data
from sqlite.
Instead, it should be sufficient to get total count once
and re-use the count value during the life of the cursor
until a requery is performed on the cursor.
(Count won't change unless data is changed - in which case
the cursor is asked to perform requery anyway. So doing count
once and reusing it should work)
Change-Id: I3520d94524dda07be9bcff56b6fbae5276af1d3b
/frameworks/base/core/tests/coretests/src/android/database/sqlite/SQLiteCursorTest.java
|
| 65a8883f0e605bb8a73a692987b47ce5da632e72 |
|
17-Jul-2010 |
Vasu Nori <vnori@google.com> |
don't store mDatabase in SQLiteCursor as it is already in SQLiteQuery
SQLiteCursor has two members: mQuery, mDatabase
but mQuery already has mDatabase.
there is no need for SQLiteCursor.mDatabase.
and everytime SQLiteQuery.mDatabase is to be used, try to use a pooled database
connection handle, if possible.
Change-Id: I42b2376d714a1a4091c843e245a45b882bb7fee6
/frameworks/base/core/tests/coretests/src/android/database/sqlite/SQLiteCursorTest.java
|