This next version is truly going to be quite a major upgrade. Ive just finished implementing Transactions within the Framework, so you can now safely call .Save() and can ensure that the database will either be commited with data or Rolled back if there was a validation problem.

Im also trying out an experimental feature which Ive never done before: In Memory transactions. i.e. I keep track of the state of the object by making a copy of it and using that copy if i ever need to rollback. Now this seems like some hair brained idea, since it means twice the amount of memory would be needed to keep track of both modified and unmodified objects. However, Ill continue implementing this, and when and IF we see any performance degradations, it will be just a compile switch away ...

Just to highlight what I mean by In Memory Transactions, check out this NUnit code fragment:


mObj2.MyString = "Two";
mObj2.BeginAtomic();
mObj2.MyString = "Three";
mObj2.BeginAtomic();
mObj2.MyString = "Four";
mObj2.BeginAtomic();
Assert.AreEqual( "Four", mObj2.MyString );
mObj2.RollbackAtomic();
Assert.AreEqual( "Four", mObj2.MyString );
mObj2.RollbackAtomic();
Assert.AreEqual( "Three", mObj2.MyString );
mObj2.RollbackAtomic();
Assert.AreEqual( "Two", mObj2.MyString );




yk.