repository caching

[Andrew Shadura]

Hello everyone,

I was reading kallithea/model/db.py and trying to understand what
Repository.update_changeset_cache does. It seems, it gets the last
changeset from the repository, and if it's the same cache thinks it is,
it does nothing, otherwise it updates the database. Is getting the last
changeset really such an expensive operation we want to do rarely? It
seems to me that this sort of caching is doing more harm than good. We
should probably call update_changeset_cache more often or, maybe, call
it every time we access the changeset cache, so any inconsistencies are
detected immediately.

What do you think about it?

-- 
Cheers,
  Andrew

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sfconservancy.org/pipermail/kallithea-general/attachments/20150901/182b8ebb/attachment.sig>