QOF
0.8.7
|
Files | |
file | qof-sqlite.h |
Public interface of qof-backend-sqlite. | |
Functions | |
void | qof_sqlite_provider_init (void) |
Initialises the SQLite backend. More... | |
The QOF SQLite backend is now mostly functional. This backend is designed for use by embedded systems where libxml2 is too large - other, larger, systems will be able to use a more comprehensive libgda backend that can connect with a variety of databases using plugins.
SQLite is typeless so the types defined for the various QOF parameter types act as more of a guide than a rule.
CREATE TABLE sqlite_kvp ("kvp_id int primary key not null", "guid char(32)", "path mediumtext", "type mediumtext", "value text", END_DB_VERSION);Entity tables therefore do not contain kvp data. Although the KVP table uses an internal ID number, all lookups are done via the GUID of the entity.
void qof_sqlite_provider_init | ( | void | ) |
Initialises the SQLite backend.
Sets QOF SQLite Backend Version 0.3, access method = sqlite:
The ID in all SQLite tables created by QOF is the GUID of the entity, expressed as a hexadecimal string.
The version number only changes if:
Initialises the backend and provides access to the functions that will load and save the data. Initialises default values for the QofBackendOption KvpFrame.
Instance KvpFrames are retrieved and stored as a separate table in the same SQLite file "sqlite_kvp". The primary key is an internal, sequential, identifier that does not need to be exposed. Each KvpValue is one record in the kvp table - frames are just a type of value. Records include fields for the path, type and value of the KvpValue as well as the GUID of the entity that holds the value.
Table name: sqlite_kvp Table values: internal_id, guid_as_string, path, type, value
At present, qof_sqlite has no QofBackendOption options and therefore no strings that are translatable.
Definition at line 1063 of file qof-sqlite.c.