title: Quartz jobs hanging around in DB tables
body: <p>We are using Quartz 2.1.6 for job scheduling on a cluster, and storing the job data in a JDBC jobstore in our MySQL database (MySQL 5.1).</p>
  
  <p>All our Quartz configuration (scheduler, jobs, triggers) is done at startup through Spring.  We store the data in the database for clustering purposes.</p>
  
  <p>Problem:  We have several jobs that were added and then deleted from the Quartz configuration.   They are no longer in the config, but they are still present in the tables.   How do we get rid of them?    Reading the Quartz documentation, it appears that doing manual edits of the tables is a Very Bad Thing.   </p>
  
  <p>We do not appear to be explicitly setting JobDetail.setDurability(true), so I'm not sure why these jobs and triggers are hanging around, but they are.   </p>
  
  <p>Anyone have an answer?</p>