In Database caching I showed how to use a cacheHandler to speed things up and avoid using up service quotas. In some cases you may hit the maximum cache size, which is 100k. The cache handler can take care of that automatically. There is no special action needed on your part.
If a put cache operation detects the data will break the cacheservice quota, it splits the data into chunks and writes a number of cache entries. The main cache item's key will end up pointing to a list of chunks that need to be put back together again.
Services > Desktop Liberation - the definitive resource for Google Apps Script and Microsoft Office automation > Database abstraction and Google Apps Script >