PersistVisitor needs to be able to detect whether or not a change occurred at some point in the persisted domain model before generating t-sql for a branch


Currently, the PersistVisitor class dutifuly visits each node in a domain model to get the required t-sql from an Update, Insert, or PersistNothing builder class which each will add to the transaction size and activities. If at any point it encounters a node at and below which there is no transactional change for: it should not generate t-sql through the builders and stop traversing. We need some means of look-ahead. Perhaps a pre-node traversal could build and flatten the list of nodes which should actually be passed to one of the builders.
Closed Jun 11, 2009 at 3:24 AM by arobson