Item 1: Allow combinations of parameters separated by commas
in job schedules
Date: 11 April 2014
Origin: Heath Petersen <Heath AT HPetersenFamily DOT com>
Status:
What: The ability to allow combinations of parameters
separated by commas would clean up some schedule
definitions.
Why: An example is the easiest way to explain this -
Schedule {
Name = "dailyWithFullEveryOtherMonth"
Run = Level=Full Jan 1st Sun at 23:05
Run = Level=Differential Feb 1st Sun at 23:05
Run = Level=Full Mar 1st Sun at 23:05
Run = Level=Differential Apr 1st Sun at 23:05
.
. Shortened for readability.
.
Run = Level=Differential Dec 1st Sun at 23:05
Run = Level=Differential 2nd-5th Sun at 23:05
Run = Incremental Mon-Sat at 23:05
}
Could be simplified to -
Schedule {
Name = "dailyWithFullEveryOtherMonth"
Run = Level=Full Jan,Mar,May,Jul,Sep,Nov 1st Sun at 23:05
Run = Level=Differential Feb,Apr,Jun,Aug,Oct,Dec 1st Sun at 23:05
Run = Level=Differential 2nd-5th Sun at 23:05
Run = Incremental Mon-Sat at 23:05
}
Notes: Comma operators could be allowed in the specification of the month,
weekday, and time. Program logic would have to expand to all combinations.
Ex: Jan,Feb 1st Sun,Wed would have to expand to Jan 1st Sun, Jan 1st Wed,
Feb 1st Sun, Feb 1st Wed.
