On Tuesday, September 3, 2013 2:08:20 AM UTC+5:30, Cédric Krier wrote: > > On 02/09/13 04:12 -0700, Kaushik S wrote: > > <field name="function">ldap_sync</field> # > This is > > the trigger function > > <field > name="args">'ldap_server','username','password'</field> > > // These are the arguments to the trigger function > > </record> > > You define to run it every 60 minutes so you must wait at least 1 hour > before knowing if it runs.
Yes. What I pasted above is a legacy code that was written as proof of concept. The actual implementation I am looking at now. > > I need to talk to an ldap server and get the latest records from a > table. I > > hope its ok to use ir.cron for this kind of a thing. If not, please > > suggest. > > It sounds strange and calling such code every minutes shall probably not > scale very well. > But without knowing more about what it is, it is difficult to give > advice. > > ok. Thanks. We are looking for changes in an external database table. This is a small database we are accessing. This table has around 10,000 records. We might have 1 or 2 entries added a month. We just have to maintain a list of all primary keys in this table. So, whenever a new entry has been added, we need to know. It would be great if we can get a notification but that is not in our control. We have to watch for new updates. What is the best way to do this? Would you say we shouldn't use a trigger at all?. Should we may be run an external daemon that looks for changes and notifies gnu health?.
