Re: Change commitment control after compilation

<Buck>
My example used L1 as the transaction boundary.
</Buck>
... if this is your point of view (it mind be appropriate for your needs), then you would just say commit in your L1 section. That might add some complexitivity, but with the aproach of having some pool of failed transactions, not too much. in case of rollback, some elementary transactions would go to the nonprocessed pools, beeing done next time (this could be a try-again routine, run 3 times - we did something like this with the high paralelliszed application)

@Henrik: thats one of the posts, thinking about wasting of time. I'm not so much interested in this 99% (maybe less of them), the rest might be more improtent to me ( must not ne your point of interest!!!)

Have a nice day (night in germany)

Dieter