Logged In: NO 

Richard:

I agree with the fact that the information for this specific 
problem is available in another way.

I don't agree that it shouldn't 
be fixed. It just seems broken
that the reactor gets an incorrect view of 
the journal. By the
time the reactor sees the journal, the transaction it 
is
responding to has been commited, but its not in the 
journal
received by the reactor.

Say I have a function that 
analyzed the data from the journal
looking for more than three entries 
into a testing state. If I
call it from an external script immediatly after 
making the
fourth test state entry, everything works fine. If I call 
the
same function from a reactor, it fails if the trigger caused 
a
transition to the fourth testing state since its not present in
the 
journal.

I would have to fake additional journal entries in my 
reactor
code to make the function work. This is really ugly.

-- 
rouilj