Morris Jobke 9737290e39 Run cleanup of expired DB file locks to background job ... * fixes #22819 The old way fired a DELETE statement on each destruction of the DBLockingProvider. Which could cause a lot of queries. It's enough to run this every 5 minutes in a background job, which in the end could result in file locks that exists 5 minutes longer - in the worst case and for not properly released locks. This makes the DB based locking a lot more performant and could result in a similar performance to the Redis based locking provider.		2016-03-04 20:13:05 +01:00
..
l10n	[tx-robot] updated from transifex	2016-03-01 01:55:33 -05:00
private	Run cleanup of expired DB file locks to background job	2016-03-04 20:13:05 +01:00
public	Revert "No longer evaluate appinfo/version"	2016-03-03 18:42:23 +01:00
autoloader.php	Happy new year!	2016-01-12 15:02:18 +01:00
base.php	Update author information	2016-03-01 17:25:15 +01:00