TopGit theo dõi square/sqlbrite trên GitHub, đã đạt 4.5k sao. A lightweight wrapper around SQLiteOpenHelper which introduces reactive stream semantics to SQL operations.
Tóm tắt dựng từ metadata GitHub của chính dự án — chưa có bài review TopGit. Trang sẽ tự động cập nhật khi bài review đầy đủ được xuất bản.
VÌ SAO CHƯA CÓ REVIEW
TopGit viết bài đầy đủ cho repo có nhiều sao nhất và được yêu cầu nhiều nhất. Trang này là snapshot trong thời gian chờ — xem README gốc ở tab READ ME.
A lightweight wrapper around SupportSQLiteOpenHelper and ContentResolver which introduces reactive
stream semantics to queries.
Deprecated
This library is no longer actively developed and is considered complete.
Its database features (and far, far more) are now offered by SQLDelight
and its upgrading guide offers some
migration help.
For content provider monitoring please use Copper instead.
Usage
Create a SqlBrite instance which is an adapter for the library functionality.
SqlBrite sqlBrite = new SqlBrite.Builder().build();
Pass a SupportSQLiteOpenHelper instance and a Scheduler to create a BriteDatabase.
BriteDatabase db = sqlBrite.wrapDatabaseHelper(openHelper, Schedulers.io());
A Scheduler is required for a few reasons, but the most important is that query notifications can
trigger on the thread of your choice. The query can then be run without blocking the main thread or
the thread which caused the trigger.
The BriteDatabase.createQuery method is similar to SupportSQLiteDatabase.query except it takes an
additional parameter of table(s) on which to listen for changes. Subscribe to the returned
Observable<Query> which will immediately notify with a Query to run.
Observable<Query> users = db.createQuery("users", "SELECT * FROM users");
users.subscribe(new Consumer<Query>() {
@Override public void accept(Query query) {
Cursor cursor = query.run();
// TODO parse data...
}
});
Unlike a traditional query, updates to the specified table(s) will trigger additional
notifications for as long as you remain subscribed to the observable. This means that when you
insert, update, or delete data, any subscribed queries will update with the new data instantly.
final AtomicInteger queries = new AtomicInteger();
users.subscribe(new Consumer<Query>() {
@Override public void accept(Query query) {
queries.getAndIncrement();
}
});
System.out.println("Queries: " + queries.get()); // Prints 1
db.insert("users", SQLiteDatabase.CONFLICT_ABORT, createUser("jw", "Jake Wharton"));
db.insert("users", SQLiteDatabase.CONFLICT_ABORT, createUser("mattp", "Matt Precious"));
db.insert("users", SQLiteDatabase.CONFLICT_ABORT, createUser("strong", "Alec Strong"));
System.out.println("Queries: " + queries.get()); // Prints 4
In the previous example we re-used the BriteDatabase object "db" for inserts. All insert, update,
or delete operations must go through this object in order to correctly notify subscribers.
Unsubscribe from the returned Subscription to stop getting updates.
final AtomicInteger queries = new AtomicInteger();
Subscription s = users.subscribe(new Consumer<Query>() {
@Override public void accept(Query query) {
queries.getAndIncrement();
}
});
System.out.println("Queries: " + queries.get()); // Prints 1
db.insert("users", SQLiteDatabase.CONFLICT_ABORT, createUser("jw", "Jake Wharton"));
db.insert("users", SQLiteDatabase.CONFLICT_ABORT, createUser("mattp", "Matt Precious"));
s.unsubscribe();
db.insert("users", SQLiteDatabase.CONFLICT_ABORT, createUser("strong", "Alec Strong"));
System.out.println("Queries: " + queries.get()); // Prints 3
Use transactions to prevent large changes to the data from spamming your subscribers.
The full power of RxJava's operators are available for combining, filtering, and triggering any
number of queries and data changes.
Philosophy
SQL Brite's only responsibility is to be a mechanism for coordinating and composing the notification
of updates to tables such that you can update queries as soon as data changes.
This library is not an ORM. It is not a type-safe query mechanism. It won't serialize the same POJOs
you use for Gson. It's not going to perform database migrations for you.
Some of these features are offered by SQL Delight which can be used with SQL Brite.
Snapshots of the development version are available in Sonatype's snapshots repository.
License
Copyright 2015 Square, Inc.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Trang TopGit này là một snapshot — tab "Readme" hiển thị nguyên văn README của repo (đã bỏ link, giữ ảnh). Repo GitHub ở github.com/square/sqlbrite là nguồn chính thức.
square/sqlbrite có bao nhiêu sao?
square/sqlbrite có 4.5k sao GitHub — tải lại trang để xem số mới nhất, hoặc xem trực tiếp github.com/square/sqlbrite. TopGit phản chiếu số sao của GitHub nhưng không cam kết đến từng phút.
square/sqlbrite có phải mã nguồn mở không?
Có — square/sqlbrite phát hành theo license Apache-2.0, nghĩa là mã nguồn mở để đọc, fork và (tùy license) tái sử dụng. Mã: github.com/square/sqlbrite.
square/sqlbrite có trang demo không?
Dự án có trang chủ ở https://square.github.io/sqlbrite/3.x/sqlbrite/. Tab "Readme" ở trang này thường có ảnh chụp và hướng dẫn bắt đầu nhanh.
square/sqlbrite là gì?
square/sqlbrite (square/sqlbrite) là dự án Java trên GitHub. Theo mô tả gốc: A lightweight wrapper around SQLiteOpenHelper which introduces reactive stream semantics to SQL operations.
Đọc đầy đủ README ở tab phía trên.
Muốn nghe thêm một ý kiến về sqlbrite?
Hỏi một AI đọc được trang này — một cú bấm là có ngay nhận định về sqlbrite.