Changes

Jump to navigation Jump to search
113 bytes added ,  12:45, 6 May 2021
* All job services will be scheduled for evaluation when the BaseX server or BaseX HTTP server is started.
* If a job service is outdated (e.g. because a supplied end time has been exceeded), it will be removed from the jobs file at startup time.
* Job services can be updated: If a new job is registered, and if there is already a job with the same id, the old entry will be replaced.
* The job definitions are stored in a {{Code|jobs.xml}} file in the database directory. It can also be edited manually.
==jobs:list-details==
 
{{Mark|Updated with Version 9.4:}} interval added.
{| width='100%'
==jobs:eval==
{{Mark|Updated with Version 9.4:5}} {{Code|log}} option : Integers addedas valid start and end times.
{| width='100%'
** The result will be cached in main-memory until it is fetched via [[#jobs:result|jobs:result]], or until {{Option|CACHETIMEOUT}} is exceeded.
** If the query raises an error, it will be cached and returned instead.
* {{Code|start}}: a dayTimeDuration, time , dateTime or dateTime integer can be specified to delay the execution of the query:
** If a dayTimeDuration is specified, the query will be queued after the specified duration has passed. Examples for valid values are: <code>P1D</code> (1 day), <code>PT5M</code> (5 minutes), <code>PT0.1S</code> (100 ms). An error will be raised if a negative value is specified.
** If a dateTime is specified, the query will be executed at this date. Examples for valid values are: <code>2018-12-31T23:59:59</code> (New Year's Eve 2018, close to midnight). An error will be raised if the specified time lies in the past.
** If a time is specified, the query will be executed at this time of the day. Examples for valid times are: <code>02:00:00</code> (2am local time), <code>12:00:00Z</code> (noon, UTC). If the time lies in the past, the query will be executed the next day.
** An integer will be interpreted as minutes. If a dateTime is the specifiednumber exceeds the minutes of the current hour, the query will be executed at this date. Examples for valid values are: <code>2018-12-31T23:59:59</code> (New Year's Eve 2018, close to midnight). An error will be raised if the specified time lies in the pastone hour later.
* {{Code|interval}}: a dayTimeDuration string can be specified to execute the query periodically. An error is raised if the specified interval is less than one second (<code>PT1S</code>). If the next scheduled call is due, and if a query with the same id is still running, it will be skipped.
* {{Code|end}}: scheduling can be stopped after a given time or duration. The string format is the same as for {{Code|start}}. An error is raised if the resulting end time is smaller than the start time.
=Changelog=
 
;Version 9.5
* Updated: {{Function|Jobs|jobs:eval}}: integers added as valid start and end times.
;Version 9.4
* Updated: {{Function|Jobs|jobs:eval}}: option addedfor writing log entries.
* Updated: {{Function|Jobs|jobs:list-details}}: interval added.
Bureaucrats, editor, reviewer, Administrators
13,550

edits

Navigation menu