138219d74a
* 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.
19 lines
415 B
XML
19 lines
415 B
XML
<?xml version="1.0"?>
|
|
<info>
|
|
<id>files</id>
|
|
<name>Files</name>
|
|
<description>File Management</description>
|
|
<licence>AGPL</licence>
|
|
<author>Robin Appelman, Vincent Petry</author>
|
|
<default_enable/>
|
|
<version>1.5.1</version>
|
|
<types>
|
|
<filesystem/>
|
|
</types>
|
|
<dependencies>
|
|
<owncloud min-version="9.1" max-version="9.1" />
|
|
</dependencies>
|
|
<documentation>
|
|
<user>user-files</user>
|
|
</documentation>
|
|
</info>
|