SQL & RestAPI Sync Adapter for Titanium Alloy Framework. The idea is to combine Restful API with a local sql database.
Simple add the following to your model in PROJECT_FOLDER/app/models/.
exports.definition = {
config : {
"columns": {
"id":"INTEGER PRIMARY KEY",
"title":"text",
"modified":text
},
"URL": "http://urlPathToRestAPIServer.com/api/modelname",
"debug": 1, //debug mode enabled
"useStrictValidation":1, // validates each item if all columns are present
"adapter" : {
"type" : "sqlrest",
"collection_name" : "modelname",
"idAttribute" : "id",
// optimise the amount of data transfer from remote server to app
"addModifedToUrl": true,
"lastModifiedColumn": "modified"
},
//optional
"headers": { //your custom headers
"Accept": "application/vnd.stackmob+json; version=0",
"X-StackMob-API-Key": "your-stackmob-key"
},
// delete all models on fetch
"deleteAllOnFetch": true
},
extendModel : function(Model) {
_.extend(Model.prototype, {});
return Model;
},
extendCollection : function(Collection) {
_.extend(Collection.prototype, {});
return Collection;
}
}
Then add the sqlrest.js to PROJECT_FOLDER/assets/alloy/sync/. Create the folders if they dont exist.
Use the debug property in the above example to get logs printed with sql statements and server respose to debug your usage of the sqlrest adapter.
Save a timestamp for each model in the database. Use the lastModifiedColumn property in the adapter config to send the HTTP Header "Last-Modifed" with the newest timestamp. This is great for improving the amount of data send from the remote server to the app.
"adapter" : {
...
"lastModifiedColumn": "modified"
},
This is tell the adapter which column to store a timestamp every time a model has been changed.
Define your own custom headers. E.g. to add a BaaS API
"headers": {
"Accept": "application/vnd.stackmob+json; version=0",
"X-StackMob-API-Key": "your-stackmob-key"
}
Lets say you are a REST API where the results are nested. Like the Twitter search API. It has the found feeds in a results object.
Use the parentNode to specify which child object you want to parse.
config: {
...
"parentNode" : "results"
}
It has support for nested objects.
config: {
...
"parentNode" : "news.domestic"
}
You can also specify this as a function instead to allow custom parsing the feed. Here is an example:
Custom parsing:
parentNode: function (data) {
var entries = [];
_.each(data.feed.entry, function(_entry) {
var entry = {};
entry.id = _entry.id.$t;
entry.startTime = _entry.gd$when[0].startTime;
entry.endTime = _entry.gd$when[0].endTime;
entry.title = _entry.title.$t;
entry.content = _entry.content.$t;
entries.push(entry);
});
return entries;
}Some times its important for the app to have some certainty that the data provided by the database is valid and does not contain null data. useStrictValidation runs through the fetch response data and only allows the items which have all columns in the obejct to be saved to the database.
config: {
...
"useStrictValidation":1
}
If you want to load/save data from the local SQL database, then add the localOnly property.
collection.fetch({
localOnly:true
});Set this property to true, if you want to get the local data immediately, and get the remote data when the server returns it.
Notice: This will trigger two fetch calls.
config: {
...
"initFetchWithLocalData" : true
}
Set this proerty to true if you want the error response object from the remote server. Default behaviour is not to return this, but return the data stored locally.
config: {
...
"returnErrorResponse" : true
}
You can perform a local query, and use a bunch of SQL commands without having to write the actual query. The query is also support btw. Use: select, where, orderBy, limit, offset, union, unionAll, intersect, except, like, likeor
collection.fetch({
data: {
language: "English"
},
sql: {
where:{
category_id: 2
},
orderBy:"title",
offset:20,
limit:20,
like: {
description: "search query"
}
},
localOnly:true
});v0.1.38
Small bugfix for model.idAttribute in sql where statements
v0.1.37
Updated to use Alloy 1.3.0.
v0.1.36
Bugfix for building the sql statement. If orderby, likeor and limit was used at the same time, the query was incorrect. This has been fixed.
v0.1.35
Added support for deleting all models on fetch. Use deleteAllOnFetch in adapter config.
v0.1.34
Added support for addModifedToUrl and lastModifiedDateFormat to better control over the outcome of Last Modified.
v0.1.33
Bugfix for special case where collection has assigned an id and hence fetch will only return a single model.
v0.1.32
Added returnErrorResponse enables the developer to get the error response object from the remote server.
v0.1.31
Bugfix for Last Modified Column.
v0.1.30
JSON.parse errors are now caught.
v0.1.29
Small bugfix. Issue when using localOnly and initFetchWithLocalData together.
v0.1.28
Added support for returnExactServerResponse which is useful for remote search.
v0.1.27
Bug fix for building sql queries. typeof array corrected to _.isArray
v0.1.26
Added support for parentNode as a function for custom parsing. thanks @FokkeZB
v0.1.25
More bugfixes
v0.1.24
Bugfix: Auto ID's are not stored when idAttribute is not set
v0.1.23
Added initFetchWithLocalData to fetch params.
Better logic for update/create. Now local db handles duplicate ids.
v0.1.22
Added initFetchWithLocalData for fetch local data before remote.
v0.1.21
Added useStrictValidation for fetch response data.
v0.1.20
Support for parsing nested result objects.
v0.1.19
Support for custom headers.
Fix for last modified column not existing on a new model.
v0.1.18
Bugfix for select statements.
v0.1.17
Added where statement that iterate an array.
Bugfix for select statements.
Optimised the localOnly request to only return data.
v0.1.16
Added combined data and sql.where queries.
isCollection check.
Bugfixes for Last Modified.
v0.1.15
Added check for model in read.
v0.1.14
Added Last Modified for data transfer optimisation & debug mode
v0.1.13
Updated for Alloy 1.0.0.GA
v0.1.12
Added urlparams and improved update rest method
v0.1.11
Advanced sql interface and localOnly added.
v0.1.10
Init
Mads Møller
web: http://www.napp.dk
email: mm@napp.dk
twitter: @nappdev
Copyright (c) 2010-2013 Mads Møller
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.