Ok, so our database has many tables that are 'segmented' in that when a field in a row changes, the old row is given an EndDate (previously null) and the row is duplicated with a null EndDate and the new field value. (Every segmented table has a BeginDate that is part of the PK, and an EndDate).

We are wanting to come up with a way to inject custom logic into the save process (adapter pattern) to allow for the segmentation to happen automatically, but so far I've been unable to come up with a way to do it. I need to be able to examine each entity being saved, determine if its a segmented table (probably via a custom property), and if so, check to see if I need to EOL the old row. My first thought was to override SaveEntity(), use ObjectGraphUtils.DetermineActionQueues() to flatten the graph and allow me to traverse all of my entities to be saved, and then deal appropriately with the segmented ones, then call base.SaveEntity(). However, this isn't an option because it doesn't allow for UOW.

OnBeforeEntitySave() won't suffice because it doesn't allow me to inject an entity into the insertion/update chain, plus we are using UOW at times, and I see that UOW now handles persistance entirely on its own so OnBeforeEntitySave() wouldn't even be called.

Frans (or anybody), do you have any suggestions?

Yes OnBeforeEntitySave is called, as it's called from PersistQueue, which is inside the dataaccessadapter.

IMHO if you use a UoW, calculate the queues up front, determine if you need to inject more entities, then add them to the uow, and persist them using the UoW, you should be able to do it. Perhaps more UoW's, in a single transaction?

Thanks Frans, I'll give that a shot.