Thu, 21 Dec 2017 19:48:27 +0100
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.
Changelog ========= version 1.1.0 (2017-10-07) -------------------------- - added TLSv1.3 config - dav-sync stores the webdav lock token in a file now - added archive command to dav-sync - added sigint handler to dav-sync - added dav remove-property command - added support for lock timeouts (dav, dav-sync) - added namespace config element - fixed that dav-sync overrides files that are not in the db but on the server - disabled automatic creation of .dav directory in dav version 1.0.1 (2017-09-21) ----------------------- - fixed dav-sync bug with large files - fixed crash when dav-sync can't delete a resource on the server - fixed wrong int type that results in a crash on some platforms - fixed dav startup without .dav directory - fixed some memory leaks - code cleanup version 1.0.0 (2017-08-06) ----------------------- - initial release (dav, dav-sync)