A ModelView
is a SQLite representation of a VIEW
. Read official SQLite docs
here for more information.
As with SQLite a ModelView
cannot insert, update, or delete itself as it's
read-only. It is a virtual "view" placed on top of a regular table as a prepackaged
Select
statement. In DBFlow using a ModelView
should feel familiar and be very simple.
@ModelView(database = TestDatabase.class)
public class TestModelView extends BaseModelView<TestModel2> {
@ModelViewQuery
public static final Query QUERY = SQLite.select().from(TestModel2.class)
.where(TestModel2_Table.model_order.greaterThan(5));
@Column
long model_order;
}
To specify the query that a ModelView
creates itself with, we must define
a public static final field annotated with @ModelViewQuery
. This tells DBFlow
what field is the query. This query is used only once when the database is created
(or updated) to create the view.
The full list of limitations/supported types are:
- Must extend
BaseModelView
- Only
@Column
are allowed - No
@PrimaryKey
or@ForeignKey
- Supports all fields, and accessibility modifiers that
Model
support - Does not support
@InheritedField
,@InheritedPrimaryKey
- Basic, type-converted, non-model
@Column
. - Cannot: update, insert, or delete
ModelView
are used identical to Model
when retrieving from the database:
SQLite.select()
.from(TestModelView.class)
.where(...) // ETC