[OGo-Bugs][Bug 1736] Add RPC to retrieve log entries since
bugs@opengroupware.org
bugs@opengroupware.org
Wed, 5 Mar 2008 16:00:00 +0100 (CET)
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug
report.
http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=1736
------- Additional Comments From awilliam@whitemice.org 2006-06-19 17:25 -------
>From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.3) Gecko/20060425
SUSE/1.5.0.3-7 Firefox/1.5.0.3
Description of problem:
Add a function to the XML-RPC like what is described in bug#1564, but accepting
one parameter (log_id), and returning log entries since that entry.
Return an array with output like the query -
SELECT log_id, object_id, obj_type, action FROM log, obj_info WHERE object_id =
obj_id AND log_id > 68720
73870:73840:Job:05_changed
73880:73840:Job:00_created
73910:73840:Job:05_changed
73960:73830:Job:05_changed
I'm writing a process to take changes from the OGo system and propogate them to
other systems. Currently working with connection to the Db and using the query
above. Logic is that the process stores the last log entry it saw (log.log_id)
and it periodically wakes up and checks for more recent log entries and if it
finds some it walks through them pushing created/changed objects to a SOAP web
service.
Since log.log_id is indexed this has so far proven to be pretty light weight.
And the daemon only has to store the number of the last log entry it saw. But
I'd like to be able to do this without connecting directly to the Db.
Version-Release number of selected component (if applicable):
TRUNK
How reproducible:
Always
Steps to Reproduce:
1.
Additional info:
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.