apscheduler
apscheduler copied to clipboard
Storing extra columns than just job id, next_run_time, and job_state.
Is your feature request related to a problem? Please describe.
I want to implement my own CustomJobStore
that subclasses SQLAlchemyJobStore
which will use extended version of table apscheduler_jobs
(some extra columns I would like to store.) But for that I have to also come up with my own CustomJob
that subclasses Job
. And for that I would have to implement my own scheduler as well that uses CustomJob
Describe the solution you'd like
Maybe there should be a BaseJob
abstract class which can be registered with the existing scheduler to make it use CustomJob
instead of Job
.
Additional context The reason I have to extend table is that I want to store some extra columns specific to business.
APScheduler 4.0 will support metadata for schedules and jobs (which are a separate concept there). Can you elaborate on your requirements? I'm inclined to support custom data in schedules (and jobs) though not as top level items.
i have a same situation now, and i am trying to rewrite SQLAlchemyJobStore. It seems that this feature will be supported on v4.0, any plan for publish v4.0 recently?