Re: Adding transactions info to mdr events

Hi Svata,
I just don't see why having the transaction events is not enough. That's 
what I meant by:

 >Wouldn't it be enough just to notify you when an outermost transaction
 >starts and ends, so that you can create checkpoints?

IMO the undo support should create checkpoints on this events and be 
able to undo/redo only to the granularity defined by the checkpoints.
I think that in this approach the transaction context is not needed, 
moreover only the outermost transaction need to be considered (I think 
that is basically what you also suggested in your e-mail).
Martin

Svata Dedic wrote:
> Hi, Martin,
> 
> Martin Matula wrote:
> 
>> Why do you need the transaction be passed into events?
> 
> 
> Well, since the events are fired asynchnronously to the transaction, one 
> can never be sure which events were generated inside a transaction, so 
> they should be grouped by the listener into one undo operation. One way 
> out of that is to receive the transaction event in the stream of MDR 
> change events, which has the order of events defined.
> IMHO the events can be fired to other listener type, from some other 
> event source but using the thread which dispatch the change events.
> 
> -Svata
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]