Matthias Mullie 6bcece22cc Don't repopulate cache with potentially lagging DB data ... getNotificationCount & getLastUnreadNotificationTime have an argument $cached that allows cache to be bypassed & read from DB. That result is then stored to cache. In practice, it seems to be used only for cache invalidation. getLastUnreadNotificationTime didn't allow to specify the DB to be read from, and EchoNotificationMapper::fetchUnreadByUser only read from slave. So when we wanted to invalidate the cache, we would end up immediately repopulating it with data from a (potentially and likely) lagging slave. I've made it accept the DB type, similar to getNotificationCount. Bug: T98421 Change-Id: Ie4b09eeb04b9827b454cb2d92ee8c674bdd59a19		2015-05-07 14:01:56 +02:00
..
AbstractMapper.php	Create TargetPage data if specified by EchoEvent	2014-08-15 00:16:41 +00:00
EventMapper.php	Revert "Revert "Merge remote-tracking branch 'gerrit/master' into two_tabs""	2014-08-14 18:46:26 +00:00
NotificationMapper.php	Don't repopulate cache with potentially lagging DB data	2015-05-07 14:01:56 +02:00
TargetPageMapper.php	Allow multiple target pages per event	2015-03-31 07:56:52 +00:00