search

sakarin / myschedule

Automatically exported from code.google.com/p/myschedule
0 stars 0 forks source link

Job & Trigger are left when DB scheduler is deleted #96

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Create DB scheduler
2. Create Job / Trigger to run
3. Delete DB scheduler

What is the expected output? What do you see instead?
1. Job & Trigger should be deleted as well

Please use labels and text to provide additional information.

Original issue reported on code.google.com by magicboo on 27 Aug 2012 at 5:51

GoogleCodeExporter commented 8 years ago 
Hello Magicboo,

What you described is expected, not a bug. 

If you were to create a database scheduler configuration, then all job and 
trigger data are persist into database. When you delete the "DB Scheduler", you 
simple deleting the quartz configuration, not the data in the database. It's 
user responsible to delete the repeating jobs/triggers from the scheduler if 
you intend not to use it anymore.

Original comment by saltnlight5 on 27 Aug 2012 at 9:03

GoogleCodeExporter commented 8 years ago

Original comment by saltnlight5 on 27 Aug 2012 at 9:03

GoogleCodeExporter commented 8 years ago 
Got it! Thanks for your reply...
But...I don't know how to delete or close this issue!

Original comment by magicboo on 30 Aug 2012 at 6:04

GoogleCodeExporter commented 8 years ago 
No problem. I have tag this issue as "Question" and I will clean them up once 
in a while.

Original comment by saltnlight5 on 31 Aug 2012 at 1:19

GoogleCodeExporter commented 8 years ago

Original comment by saltnlight5 on 31 Aug 2012 at 1:19