Writing to parse.com was fairly complex, with all the asynchronicity and limiting. Writing the workbook to scriptDB should be much easier. We'll use exactly the same approach as for Updating parse.com , namely get the data, get the existing contents of the DB, update with any additions or modifications, delete nothing.
I already have a silo class for scriptDB partitioning - which would be kind of analogous to the parse Class, and caching to abstract getting data from sheets- like the Google visualization data fetching , so the structure can be more or less the same.
Here's the whole application - a whole lot simpler than the parse version. But it takes so long to run. I'll do some benchmarks of all the variations at the end of this, but as usual, I hit the dreaded "execution time exceeded", so I have to run it a couple of times to get all the rows done.
I am using the batching built in to the silo class for scriptDB , and buffering to the same level as in the parse version. I haven't bothered throttling as it's not required for scriptDB.
For more on parse.com see Parse.com
Services > Desktop Liberation - the definitive resource for Google Apps Script and Microsoft Office automation > Parse.com >