Support get_many, set_many, and delete_many Cache operations about python-diskcache HOT 7 CLOSED

I agree this is a useful feature. Thank you for the code snippet. Pull request welcome.

from python-diskcache.

You might want to use Django caches .get_many()/.set_many() interface, just to not add new one :)

from python-diskcache.

Do get_many and set_many operations have to hit database only once?

from python-diskcache.

Can't see if that is important, this should obviously be more efficient than a cycle of gets or sets, but otherwise implementation could be arbitrary.

from python-diskcache.

As I've thought about it, I doubt you could do get_many or set_many in a single database query but you could do them in a single database transaction. The database should be smart about which pages it updates and syncs.

So, yes, those methods should use a single database transaction.

Also, I don't think any batching should be done inside those methods. I want batching left to the end-user. If we give them an API like I've described above then the end-user can easily batch keys/values (as they may want in the case where the number of keys/values is very large). Not batching will block concurrent writers but the scenario is similar to writing a large value.

from python-diskcache.

In v4, diskcache will support transactions. There will be a tutorial section on transactions that will show how to do the *-many variants in one transaction.

from python-diskcache.

The set_many example was added to the Transactions section of the tutorial at 126b033

from python-diskcache.