Hi,
The UnitOfWOrk object seems to be useful when you have a lot of objects to update...you Put them in the UnitOfWork and them commit the whole thing. As the script sample in the SDK says:
'* IUnitOfWork contains a caching mechanism for IEntity instances
'* It caches registered objects and delivers them
'* from the cache instead of realoading them.
Just to clarify: does this mean that all those changes that are Put in the UnitOfWork are treated as a transaction (as in all or nothing) or would one have to explicitly set up transactions for that?
What would be the difference with opening a Transaction on the Connection object and then running thru the Objects Saving them and then committing the Transaction at the end?
thanks,
Rob.