You are here: Offline Data Access API

Offline Data Access API

The Offline Data Access API allows you to store data onto the device store persistently (data is made available even after application or device restart). You can access this data even when the device is offline, i.e, the device is not connected to any wireless network (cellular or WiFi). The Offline Data Access API has the following API libraries:

Local Storage API Library

Allows users to store and retrieve data in HTML pages from all the windows in the same domain even if the browser is restarted.

The data stored using the LocalStorage APIs is accessible only from the client-side as opposed to the data stored in cookies (accessible from both client-side and server-side).

Note: From V9 SP2 onwards, the Local Storage APIs’ data for a Volt MX Iris App Viewer child app is stored in child app data and not under the parent app. This feature is applicable for iOS, Windows, and Android platforms.

The Local Storage API Library contains the voltmx.store Namespace and related functions:

To store data items in a key-value format in the Local Storage, use the voltmx.store.setItem function. Use the voltmx.store.key function to retrieve the name of an existing key. Using the voltmx.store.length function, you can find the amount of the local storage. To retrieve a stored value, use the voltmx.store.getItem function. Use the voltmx.store.removeItem function to remove a data item from the local storage. To empty the database, use the voltmx.store.clear function.

To view the functionality of the Data Access API in action, download the sample application from the link below. Once the application is downloaded, build and preview the application using the Volt MX App.

Web SQL API Library

Allows users to manipulate client-side databases using SQL. Use these APIs to store data in databases that can be queried using a variant of SQL.

The Web SQL API Library contains the voltmx.db Namespace and related functions:

Open a specific version of the database using the voltmx.db.openDatabase function. You can then create an SQLTransaction object using the voltmx.db.transaction function. Use the voltmx.db.readTransaction function to read a specific transaction. Execute an SQL statement using the voltmx.db.executeSql function. Use the voltmx.db.sqlResultsetRowItem function to retrieve the row available at a specific index. You can also verify if there is any schema update and then change the version of the database being used by using the voltmx.db.changeVersion function.

Important: WebSQL implementation utilizes the database engines bundled along with the underlying SDK (SQLite in most of the cases). Volt MX Iris Platform ensures that the WebSQL semantics are same across platforms, but the uniformity of SQL semantics across native platforms is not guaranteed. For example, the WebSQL APIs have no control over the way CONSTRAINTS are supported as per the SQL92 specification. For more information on SQLite refer Appendix.

Important: WebSQL APIs are not supported on Internet Explorer and Firefox web browsers.

Important: The framework does not store the password argument to voltmx.db.openDatabase() function, it is the responsibility of application developer to secure the password.

Limitations

This section describes the limitations of WebSQL APIs:

• Table names and Column names are case-sensitive. For example, “Employee” and “employee” refer to two different tables. It is observed that table names and columns name are case-insensitive on Android platform, but case-sensitive on iPhone platform. For a cross platform uniform behavior, assume that the table names and column names are case-sensitive.

• When using the binding “?” placeholders, ensure that the number of binding parameters and the number of values are the same. Else, the database can be inconsistent.

  For example, the following statement can cause the database to be inconsistent as the number of binding parameters are 6 and the number of values are 3:

  local stmt3 = “insert into EMP_DETAILS values(?,?,?,?,?,?)”

voltmx.db.executeSql(tx,stmt3,{
    '1', '2', '3'
    }, successCallback,errorCallback);
    

• Nested database transactions are not supported across platforms. Avoid starting a new transaction in the successcallback function of an existing transaction.
• The error codes might vary between the platforms. This is due to the fact that underlying SDKs do not expose all the errors that can be mapped to HTML5 WebSQL Specification. The application should not build its business logic around these error codes. These error codes are only for diagnostic purpose.
• Accessing insertid key in the resultset rows leads to an error in SPA.
• The WebSQL APIs are not supported on Internet Explorer and Firefox.

The actual database used for storing the data and its visibility to other applications is defined in the following table:

The following table indicates the JavaScript datatypes and their corresponding SQLite datatypes: