docs/src/lock.md@bacb54502b24
docs/src/lock.md
Thu, 21 Dec 2017 19:48:27 +0100
- author
- Mike Becker <universe@uap-core.de>
- date
- Thu, 21 Dec 2017 19:48:27 +0100
- changeset 359
- bacb54502b24
- parent 320
- 12ed560c926c
- permissions
- -rw-r--r--
davql: allow ANYWHERE keyword in SELECT statements
This may seem pointless, but users might want to be explicit about this and the grammar is more consistent.
This commit also adds some no-ops to the functions body of the SET parser, because some day the grammar might allow more clauses after the WHERE clause.
--- title: 'dav lock' --- **`dav lock [-pc] <url>`** Creates a lock on the resource specified by the *url*. The lock is an exclusive write lock with infinite depth. If the resource is successfully locked, a lock token for this resource is printed to stdout. This lock token should be saved somewhere to unlock the resource eventually. **`-p`** disable file name and path decryption if enabled **`-c`** enable file name and path decryption **`-T <seconds>`** specify the lock token timeout in seconds ### Example 1: lock resource and use the lock token $ dav lock myserv/resource opaquelocktoken:0454905e-f2ff-45c4-a3d7-5c4e4db5ce37 $ dav put -L opaquelocktoken:0454905e-f2ff-45c4-a3d7-5c4e4db5ce37 myserv/resource newfile $ dav unlock -L opaquelocktoken:0454905e-f2ff-45c4-a3d7-5c4e4db5ce37 myserv/resource
