Say an entity Customer has an Orders collection and there is a method UpdateCustomer(CustomerEntity ce) that saves the changes of both the parent entity and its collection in one call.

Adding/Editing orders in the collection are easy to be reflected in the DB using adapter's SaveEntityCollection, but what do you suggest for deleting orders (w/o adding a different method)?

Is there a way for the client to 'flag' them as removal candidates and have the method walk through the collection, delete those flagged ones and save the rest?

Not at the moment. (A unitofwork object is in the works at the moment as part of the runtime upgrades). What you could do is remove the entity from the collection in the grid (as it is removed from the grid as well) and add it to a collection solely for deletion purposes, then simply use DeleteEntityCollection() to delete the entities in 1 go. To make this happen in the same transaction as the saves, start a transaction first by calling StartTransaction, then call the persistence functions like save and delete.

I see. In other words, I have to be explicit in the method declaration about this second collection, e.g. UpdateCustomer(CustomerEntity ce, EntityCollection deletedOrders), where ce.Orders will contain the remaining order entities that are either new or edited ones.

Thanks Otis.

obzekt wrote:

I see. In other words, I have to be explicit in the method declaration about this second collection, e.g. UpdateCustomer(CustomerEntity ce, EntityCollection deletedOrders), where ce.Orders will contain the remaining order entities that are either new or edited ones.

Yes.