I think it will be quite hard to implement this ex-post. But I see it as important. Especially for integration with other systems. If its there, this domino-transaction should be able to participate in 2-phase-commit transactions of J2EE/EE5. This would make integration of Domino applications in SOA architecture or J2EE/EE5 a lot more straight forward.

Yeah, DominoTxn! :-D

Sorry, couldn't resist. ;-)

Axel is absolutely right: It would be great for integration, but HARD to implement. VERY HARD!

This has been one of the gaping weaknesses for Domino. How many times have complex document hierarchies and relationships been corrupted when a process only completes half the changes because of an "object variable not set error" ?

I would like the idea of a commit/rollback in script. Seeing as document models can take any shape, something like a "Transaction Start" and a "Transaction Commit" commands in your code would be great.

I suppose the caveat would be that transaction command pairs (ie start/commit) would have to be in the same sub. I think this would only work in a scheduled agent to. Because re-running the log would be way to hard from UI. The next step would be working out how to link transaction dependancies between subs so if an error occured in a called sub that the rollback would be reported to the calling sub so it could take action in completing the roll-back...

The other problem would be storing the log somewhere in cases where people are modifying very large collections of documents, the log would be humungous. Probably from a transaction server/file store ?

Not so simple.. but if it could be done, it would put all those relational zealots in their place.. LOL.. Thumbs up from me... I wish people who demote ideas justified their answer. It may provide some insight in refining the idea...