Hi,

I'm using LLBLGen 2.6 and I wonder why the method ConstructSaveProcessQueue() does not filter the entities to update on Dirty == true. Instead each not new entity is put into the update queue.

Any reason for this?

I send the changes made during a edit cycle over the line and after the commit( with refetch == true) it is not possible the check if the entity was really just updated or if it was a new entity.

Christoph

All entities which are dirty + all entities which have pending FK syncs are placed in the queue. If your entity isn't 'dirty' but will get an fk field set due to a PK entity which is saved as well, (e.g. no order fields were changed but you assigned a new customer entity to that order), the entity WILL get dirty during the save process, hence the extra requirement.