c2c-oerpscenario team mailing list archive

[Thibaut DIRLIK <816858@xxxxxxxxxxxxxxxxxx>]

@Vo Minh Thu :

Thanks for your answer. That's exactly what I did before I saw your
merge proposal. The question is that with your version, from what I
understood, each task is run in a separate thread. Is there a way to
lock the database or something like this ? Do we have to use locks in
our cron executed code or is there a way to do this thanks to OpenERP ?

@Raphaël :

Yes, indeed this could nice ! +1 ;-)

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/816858

Title:
  ir.cron can't be inherited properly

Status in OpenERP Server:
  Invalid

Bug description:
  Hi,

  I'm working on ir.cron to extend its possibilities, but it can't be
  inherited easily. The problem is that when the server starts, the
  method _poolJobs of ir.cron is called. This method reference itself
  with this line :

  self.setAlarm(self._poolJobs, next_call, db_name, db_name)

  The problem is that if you inherit ir.cron, the _poolJobs method will
  not reference the new object, but keep referencing the old one. This
  means that if you redefine _callback() in your new ir.cron, it will
  never be called.

  I think that a small fix could be to use setAlarm on
  self.pool.get('ir.cron')._poolJobs ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/816858/+subscriptions