add an option to stop a cron after the first execution (wishlist)
Bug #636607 reported by
Servabit OpenERP team
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Odoo Server (MOVED TO GITHUB) |
Won't Fix
|
Wishlist
|
Unassigned | ||
Bug Description
we added an option to stop a cron object after the first execution
a patch is included
"This patch is applied to ir.cron object.Using this patch is possible to
delete the cron after the execution ( just adding to function called by
cron an argument with value 'kill'). It is used especially after a
modification to the database structure for upgrading the information"
Revision history for this message
| Servabit OpenERP team (openerp-servabit) wrote | #1 |
| Changed in openobject-server: | |
| importance: | Undecided → Wishlist |
Revision history for this message
| Olivier Dony (Odoo) (odo-openerp) wrote | #2 |
| Changed in openobject-server: | |
| status: | New → Won't Fix |
To post a comment you must log in.
Hello Servabit team,
A cron job can be set to have only 1 execution (number_call = 1) in which case it will stop executing after the first time.
If you need the cron to disappear as well from the list, the job can also delete itself from ir.cron during its execution (this is now properly supported in OpenERP v6.0)
As a result, we feel that adding this option in the official server would only make ir.cron objects even more complicated to use.
Thanks for reporting and providing a patch for the community to use, though!