Just wondering if there are any plans to add the ability to distribute the cache (and so keep it turned on) if accessing the DB through various instances of SQLObject?
Just spent a few minutes going through the code so I'm not sure of this is feasible, but it seems to me that one easy solution would be to write the cache to a file on disk (mounted NFS disk (ram disk?)). Since all instances are reading/writing the same data, there's no need to turn the cache off...
The caching module can be redesiged to take in a caching 'strategy' which looks like a dict. Internally, the strategy could implement the cache as a simple dict (default) or a distributed cache through the file system or a database etc.