search

Rykian / clockwork

A scheduler process to replace cron.
MIT License
544 stars 66 forks source link

Enforce uniqueness of job names #27

Open ChaoticBoredom opened 7 years ago

ChaoticBoredom commented 7 years ago

As was discussed briefly in PR #22 we should probably enforce uniqueness of jobs being passed to clockwork. Non-unique names could potentially cause confusion when debugging, and when the expectation is that the name is unique.

NOTE

This does not change the behaviour of the DatabaseEvents, beyond ignoring the new flag being passed. I am admittedly not familiar enough w/ DatabaseEvents to say whether this is a desirable change or whether this works w/ the current implementation of DatabaseEvents. Help in that area would be greatly appreciated :)

darena commented 7 years ago

In my application, I set a unique constraint on the name column.