commit | b030dcb5b7a62854c0bfe85bf04eaf60caeb83bb | [log] [tgz] |
---|---|---|
author | Yigit Boyar <yboyar@google.com> | Fri Jan 20 10:52:25 2017 -0800 |
committer | Yigit Boyar <yboyar@google.com> | Thu Jul 06 16:21:55 2017 -0700 |
tree | 09c0d884bf0b7041478f265efbf04ab8f58b1b6e | |
parent | 7c63d6b4d54e7ce5150231c152c30dcec9ebe2f2 [diff] |
Bind Cursor queries in a type safe API The rawQuery API in SQLiteDatabase class expects all bind arguments as Strings. Even though this usually works fine for other types due to SQLite's type affinity logic, it fails in some cases. To avoid that, this CL replaces the usage of rawQuery with a new class called SupportSQLQuery which has a callback to bind items to a query using the prepared statement. There is no public API to achieve this so this CL adds a new method to SupportSQLiteDatabase that accepts SupportSQLiteQuery. In the framework version, this method is implemented using a CursorFactory. This callback is not necessarily instantly invoked so to avoid the risk of binding to wrong values (because method parameters may change after the call), the SupportSQLiteStatement is prepared instantly. For this reason, we have a pooled RoomSQLiteStatement class that implements the SupportSQLiteProgram API and can rebound its parameters into another SupportSQLiteProgram. In queries, we instantly populate it and it can be re-run any later time. This implementation also avoids creating inner classes for each query. Bug: 32342709 Bug: 34503410 Test: RoomSQLiteQueryTest, QueryWriterTest, DaoWriterTest Change-Id: Id74ba3e02d8de1f7df839249327b3baf933f5f84
We are not currently accepting new modules, features, or behavior changes.
NOTE: You will need to use Linux or Mac OS. Building under Windows is not currently supported.
Follow the “Downloading the Source” guide to install and set up repo
tool, but instead of running the listed repo
commands to initialize the repository, run the folowing:
repo init -u https://android.googlesource.com/platform/manifest -b ub-supportlib-master
Now your repository is set to pull only what you need for building and running support library. Download the code (and grab a coffee while we pull down 7GB):
repo sync -j8 -c
You will use this command to sync your checkout in the future - it’s similar to git fetch
Open path/to/checkout/frameworks/support/
in Android Studio. Now you're ready edit, run, and test!
If you get “Unregistered VCS root detected” click “Add root” to enable git integration for Android Studio.
If you see any warnings (red underlines) run Build > Clean Project
.
You can do most of your work from Android Studio, however you can also build the full support library from command line:
cd path/to/checkout/frameworks/support/ ./gradlew createArchive
Run FooBarTest
Run android.support.foobar
Support library has a set of Android applications that exercise support library code. These applications can be useful when you want to debug a real running application, or reproduce a problem interactively, before writing test code.
These applications are named support-*-demos (e.g. support-4v-demos or support-leanback-demos. You can run them by clicking Run > Run ...
and choosing the desired application.
cd path/to/checkout/frameworks/support/ repo start my_branch_name . (make needed modifications) git commit -a repo upload --current-branch .
If you see the following prompt, choose always
:
Run hook scripts from https://android.googlesource.com/platform/manifest (yes/always/NO)?