Olivier Dony
9b6f5dca9a
A programming error during an older refactoring lead to the scheduler working with a single monolithic transaction. This could cause unnecessary resource contention, plus undesired rollback of all previous operations in the event of an exception during scheduling. bzr revid: odo@openerp.com-20130701163532-8bekn7sbb99ua08c
32 lines
1.3 KiB
XML
32 lines
1.3 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<openerp>
|
|
<data noupdate="1">
|
|
|
|
<record forcecreate="True" id="ir_cron_scheduler_action" model="ir.cron">
|
|
<field name="name">Run mrp scheduler</field>
|
|
<field eval="False" name="active"/>
|
|
<field name="user_id" ref="base.user_root"/>
|
|
<field name="interval_number">1</field>
|
|
<field name="interval_type">days</field>
|
|
<field name="numbercall">-1</field>
|
|
<field eval="False" name="doall"/>
|
|
<field eval="'procurement.order'" name="model"/>
|
|
<field eval="'run_scheduler'" name="function"/>
|
|
<field eval="'(False,True)'" name="args"/>
|
|
</record>
|
|
|
|
<record id="sequence_mrp_op_type" model="ir.sequence.type">
|
|
<field name="name">Stock orderpoint</field>
|
|
<field name="code">stock.orderpoint</field>
|
|
</record>
|
|
|
|
<record id="sequence_mrp_op" model="ir.sequence">
|
|
<field name="name">Stock orderpoint</field>
|
|
<field name="code">stock.orderpoint</field>
|
|
<field name="prefix">OP/</field>
|
|
<field name="padding">5</field>
|
|
<field name="number_next">1</field>
|
|
<field name="number_increment">1</field>
|
|
</record>
|
|
</data>
|
|
</openerp> |