You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When adding a new job (add_job), or altering an existing user-defined job (alter_job), it would be nice to be able to give it a custom name. When a database has more than a few custom jobs, seeing "User defined job" is not as useful to figure out which is running.
Implementation challenges
alter_job could get tricky if you want to prevent users from renaming built-in jobs. So I'd settle for add_job having the parameter.
The text was updated successfully, but these errors were encountered:
What type of enhancement is this?
API improvement, User experience
What subsystems and features will be improved?
Policy
What does the enhancement do?
When adding a new job (
add_job
), or altering an existing user-defined job (alter_job
), it would be nice to be able to give it a custom name. When a database has more than a few custom jobs, seeing "User defined job" is not as useful to figure out which is running.Implementation challenges
alter_job
could get tricky if you want to prevent users from renaming built-in jobs. So I'd settle foradd_job
having the parameter.The text was updated successfully, but these errors were encountered: