scriptDb JavaScript api examples

The JavaScript client is very similar to A VBA API for scriptDB, so reading that will give you a more detailed flavor of what can be done. The implementation is very different though, and there are a few complications you need to watch out for. 


Everything about this API happens asynchronously. POSTS are batched up, and although most of this is hidden and shouldn't provide too much difficulty for the javasScript developer, some care needs to be taken. jQuery promises are used throughout and can be used to test completion of requested operations.

Test data

We'll use exactly the same data as was used in - nosql database for - noSQL database for GAS and the same database and Google Apps Script handlers as used by A VBA API for scriptDB. The term 'class' in these examples refers to a group of objects which are stored in a scriptDB against a particular siloID, and is somewhat similar to the definition of a class.

Rendering results

For our tests, we'll render all results in <div> elements in the testing web page using this simple function
function renderScriptDb(control,id) {


Here's how to count how many objects of class 'VBAParseCustomers' are in the scriptDB described by the entry 'dbTest', and shows the result (or the error) on a web page element

    .done (function (data,cob) {
    .fail(function (data,cob) {

This one show all objects for customers in the United States
    var dbCustomer = getScriptDb("VBAParseCustomers","dbTest");
    dbCustomer.getObjectsByQuery({country:"United States"})
        .done (function (data,cob) {

See how the .getCount() and .getObjectsByQuery() function are executed asynchronously, and the results are only available for rendering when the the promise they return is resolved (or rejected).

POST examples and explanation

Functions which POST data (as opposed to GETting data) are more complex. This is because POSTS are batched (when you execute a POST, the API might not actually execute that POST until there is more to do - this helps to avoid scriptDB rate limits. Note also that the Google Apps Script handler (which deals with requests for both this and A VBA API for scriptDB), also does its own batching. Finally, it can't be guaranteed that your requested POSTS happen in the order that you execute them, since that is the nature of asynchronous requests.

DELETE, UPDATE and CREATE are all POST type operations. 

Here's an example of how you would do a POST type operation

db.createObjects([some objects...])
    .done( function (data) { worked..})
    .fail( function (error) { failed..});

At first this looks not much different the GET operation, and in fact will not be resolved until all the objects have actually been finally handled by the Script Apps handler as part of some future batch operation. However, when you are done with all POST operations , you need to execute a finalFlush(). Although flush() is executed from time to time as the queue of requests builds up, there will usually be a queue of some size to empty out. This ensures that any request which are still in the batch queue get executed. So your final operation needs to be


.finalFlush() follows .createObjects(), and .createObjects() will not be resolved until .finalFlush() is. This guarantees that any objects you have posted have indeed been completed. You can use the promise returned by .finalFlush() to know that there is nothing more to do. Note that different POST operations are dealt with in the same batch, so there is only a need for one finalFlush() per scriptdb object.

The following example copies a couple of classes from one scriptDb to another, and excercises all the concepts mentioned above. 

There's a few things of note here
  • Both copy operations will be executed simultaneously, and we don't care and can't predict which one will finish first. See trace from browser below.
  • Each dbCopy will return a promise. We can use this to postpone the counting  of the results until the copy is done.
  • testCopy itself will return a promise that will only be resolved when both copies are completed. Here's how I use the result of the testCopy to do some queries and some further processing I don't want to execute until both copies are complete.
            .done (function() {
               // do a query------
               var dbCustomer = getScriptDb("VBAParseCustomers","dbTest");
               dbCustomer.getObjectsByQuery({country:"United States"})
                    .done (function (data,cob) {
                // look up date in another table based on data in another
                var dbData = getScriptDb("VBAParseData","dbTest");
                // restrict to paricular customers
                dbCustomer.getObjectsByQuery({country:"United States"})
                    .done (function (data,cob) {
                        for ( var i = 0 ; i < data.results.length;i++) {
                            printTransaction (dbData,data.results[i]);
            function printTransaction (dbData,result) {
                    .done (function (transaction,cob) {
                        if (transaction.results.length) {
                                 }) + '<br>');  

You can get me on Google plus, Twitter or this forum. For more on this, see scriptDB API for JavaScript

For help and more information join our forumfollow the blogfollow me on twitter