Roundup 0.5.5, cygwin python.

In a reactor, I am 
attempting to discover who changed
the assignedto attribute 
(that caused my reactor
to fire) by looking at the change history 
of the issue.

I can get a list of the history inside my reactor, 
but the
last change is missing from the list.

The ideas 
that come to mind are:

  a missing commit to disk for the 
database between
       the auditor and reactor triggers

  
db.history/db.getjournal functions do not use the
       cached 
database

I have taken a brief look through the 
back_anydbm.py
file and I think these are both the problem, 
but I am not sure how to solve it.

It looks like the call 
sequence is

  fire auditors
  call db.addjournal
     which 
calls doSaveJournal
      which calls getCacheJournalDB
  fire 
reactors

in the reactor code I call:

  
history.getAttributeHistory (my library)
      db.history  (wrong 
docs btw. return 5 tuple not 4)
          db.getjournal
              
db.opendb(filename)
         
I think the problem is that the change 
to the assignedto
field is still in the cached database (since it 
shows up in the web page), but getjournal is not using the 
cache
and therefore missing the data I need.

-- rouilj