Database abstraction with google apps scriptThis is the the driver for DB.SCRATCH described in
The library reference is MTnrkatWa6Lrta8eAg6_H0qi_d-phDA33
Note that this technique relies on the predictability of CacheService. Google warn that it's not necessarily predictable, so at this point I'm not sure how robust this approach is, but I have many people out there using this now and haven't had any issues reported. Having said that, its use is intended for testing, logging and so on in preparation for and in advance of moving to a more permanent back end
This driver uses cache to provide transient database storage. By default it lives for 1 hour, but its lifetime is extended each time it is accessed. It is ideal for early testing in preparation for other backends or passing data back and forwards between co-operating processes. It can handle much more data than the Properties service, and can be protected using cache communities.
There is no authentication required, since it uses cache - normal auth will apply. However here are some tips for using this database for collaboration. You need to invent your own codes to name database elements so may as well start with a plan.
Transactions, Locking and rollback are all supported by this driver. In addition, results are cached just like any other driver. In this case, the mechanism which prolongs lifetime will not be invoked.
See more like this in Database abstraction with google apps script
Services > Desktop Liberation - the definitive resource for Google Apps Script and Microsoft Office automation > Database abstraction and Google Apps Script >