Hi DenisK,
Yes, I understand what you mean, no one will delete records at Management Studio level but this is very common in multi users environment. If a user uses your application to delete a record, you will have the same problem on your side.
Clearing the cache is ok but it is not what I expect. I want my application has such behavior.
When a user open a Customer detail screen, for instance, it will first check this Customer if it exists in cache.
If yes, it will show the screen with the cached version of this Customer and run a query with DataSource stragety to refresh data.
If No, it will get data from DataSource and then show to user.
If we have error from getting data from server, the user can still work with the cached version of the Customer.
Clearing the cache will disable this idea and will show empty data or raise error. Moreover, the application will not have "Offline" feature, the main reason that we choose to use DevForce.
Is there anyway to access related entities that are queried along with the root entity using "Include" to pre-process them before they are merged with the EntityManager's cache?