The "schedulePattern", in a mature way, uses Cron format to store the users' schedule is a good idea for running task.
This format is simple but sophisticated. In relational database, there would be some performance benefit if you seperate every "entry" of Cron to a column of table with suitable indexes.
The effort, however, is the translation between this format and user interface. And the raw data to which user input should be recorded originally.
I would design two kinds of table, one for raw data inputted by user, another for running task for schedule.
发布评论
评论（1）
“schedulePattern”，以一种成熟的方式，使用 Cron 格式来存储用户的日程安排。运行任务的好主意。
这种格式简单但复杂。在关系数据库中，如果将 Cron 的每个“条目”分离到具有合适索引的表列中，将会带来一些性能优势。
然而，工作量是这种格式和用户界面之间的转换。以及最初应该记录用户输入的原始数据。
我会设计两种表，一种用于用户输入的原始数据，另一种用于运行计划任务。
The "schedulePattern", in a mature way, uses Cron format to store the users' schedule is a good idea for running task.
This format is simple but sophisticated. In relational database, there would be some performance benefit if you seperate every "entry" of Cron to a column of table with suitable indexes.
The effort, however, is the translation between this format and user interface. And the raw data to which user input should be recorded originally.
I would design two kinds of table, one for raw data inputted by user, another for running task for schedule.