List of "one-way migrations" that define the current DB schema.
List of "one-way migrations" that define the current DB schema... See the Database overview.
Returns a ContentQuery referring to all rows in one of the tables of this database, which may be used directly, or used to seed a RecordManager for the ORM.
Close the facility.
Close the facility.
First, decrements the "nested open" count. If it has reached
zero, do a "real" close, using the protected realclose method.
Otherwise, some other activity is still using the facility, and
it stays open.
When the last activity or service calls close, the facility
actually does shut down, using the protected realClose method,
which will shut down threads, close files, or whatever.
Tag for the facility to use in log entries
Tag for the facility to use in log entries
Get a readable Android SQLiteDatabase object, for direct invocation
of core APIs.
Get a writable Android SQLiteDatabase object, for direct invocation
of core APIs.
Writes a debugging log method, using the facility's logTag
Writes a debugging log method, using the facility's logTag
Invoked when the database is created.
Invoked when the database is created. Default behavior is to
run through the complete list of schemaUpdates.
Invoked when the database is created.
Invoked when the database is created. Default behavior is to
run through the sublist of schemaUpdates from the prior version
to the end (which defines the current version).
Open the facility.
Open the facility.
If the facility isn't already open, does setup which depends on
the particular facility (which may involve opening files,
starting threads, or whatever) --- a "real" open, using the
protected realOpen method. The given Context may be used
for setup, depending on the nature of the facility.
If it is already open, just increments a "nested open" count;
see close below.
Schema version.
Schema version. By default, the length of the schemaUpdates list.
Primitive base for database singletons. For most purposes, you'll want to use Database instead, for its extra convenience features. ThreadlessDatabase is available for cases where the conveniences are getting in the way.
Manages setup and schema upgrades, and makes the tables database available as Positronic Net ContentRepositorys which can be queried directly, or manipulated via the orm. Further comments on how this works for Database also apply here.
Note that
opening a Database does not trigger any I/O; that action is delayed until the first query (at which point we also perform any schema updates, etc.). It is strongly recommended that this not be done on anActivitymain UI thread.