Hi

I am curious what is the difference between saving a graph of entities and saving each enitity in graph.

for example if we have N entities, they can be saved as this :

//start transaction SaveEntitiy(entity1) ... SaveEntitiy(entityN) //commit transaction

or they can be grouped together in a graph of entities with root of ROOT and then saved as this :

//start transaction SaveEntity(Root) //commit transaction

What is the difference? which one is faster?

//start transaction SaveEntity(Root) //commit transaction Would be the way that I would go. The entities keep track of whether or not they are dirty and need to be saved, which may cut down on your calls to your database right there.

Like Paul said, better to save them as a graph with a call to save the root enity. I would add that this save internally starts a transaction, so you wouldn't need to start your own.