Skip to content

An EnyoJS plugin, implementing data source using underlying WebSQL

License

Notifications You must be signed in to change notification settings

vtomilin/EnyoWebSQLSource

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

6 Commits
 
 
 
 
 
 
 
 

Repository files navigation

Installation

websql.Source is installed into your project's lib directory, much like any other Enyo plugin, for example layout or onyx. See this post in Enyo Wiki for details.

Generally, you want to add websql.Source plugin as a git submodule of your project, placed under lib/indexeddb directory.

One way to do that is to run the following at your project's root directory:

git submodule add https://github.com/vtomilin/EnyoWebSQLSource.git lib/websql

Then you should add websql.Source dependency to your top-level package.js file:

enyo.depends(
    '$lib/layout',
    '$lib/onyx',
    '$lib/websql',
    // Other dependencies...
);

Usage

This code is to be run when application instance is initialized.

try {
    var webSqlSrc = new websql.Source({
        dbName: 'food',
        dbSchema: MyApp.Resources.schema,
        dbSchemaDidUpdate: function(e) {
            if(e) {
                enyo.error('Failed to create database schema:', e);
                
                return;
            }
            
            enyo.store.addSources({sql: webSqlSrc});
        }
    });
} catch(e) {
    enyo.error(e && e.toString());
}

It will create(or open if it already exists) a database 'food' using SQL statements, provided in MyApp.Resources.schema string.

In the above example, MyApp.Resources is a singleton, containing application resources, such as database schema SQL statements.

Once schema is created/updated, in this particular example, a special global onWebSQLDbReady signal is sent such that the other parts of the app could make use of the data in the database.

You can now save and retrieve your models using WebSQLSource source, registered under sql name in this particular example. Further, in the following example, involving retrieving models from the database, it is assumed there is a table diet in the database. The table property indicates the table, which ennyo.Collection is pupulated from. Note that you could use url property instead for that same purpose as you subclass enyo.Collection and enyo.Model as well. The url property could be your usual url, i.e. http://myserver.com/data as long as data at the end of the url is the database table where your data is.

var data = new Collection();
data.fetch({
    table: 'diet',
    source: 'sql'
});

this should work also:

var data = new Collection();
data.fetch({
    url: 'diet',
    source: 'sql'
});

so as this

enyo.kind({
    name: 'MyDiet',
    kind: 'enyo.Collection',
    url: 'http://w8management.com/diet'
});

var diets = new MyDiet();
diets.fetch({source: 'sql'});

Additionally, options object, a parameter to fetch method, may take the following properties:

  • opts.table Provides table name. Optional, if not specified, then the table will be deduced from the model's url property.
  • opts.attributes Optional model attributes.
  • opts.where Optional 'Where' clause. DO NOT include word where. Use ? to specify arguments. See opt.args also.
  • opts.orderBy Order By clause. DO NOT include words order by
  • opts.limit limit clause to limit number of rows, fetched
  • opts.offset offset clause, see SQL spec for details
  • opts.args An array of arguments to use in conjunction with ? templates, specified in where or elsewhere. The number of array elements must coincide with total number of ? templates.

About

An EnyoJS plugin, implementing data source using underlying WebSQL

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published