Thanks for your suggestions. That's a very nice documentation there.

In my case the whole idea behind using a common EntityManager for the application is "better performance".

When the same page is revisited, we don't want to load all the data again from database. If we make use of cache, then we save lot of time.

But in other way, we don't want to keep the outdated entities in cache. It is possible that some thing might have been updated in database from some other client. So at certain intervals we want to remove SPECIFIC(not all) entities from cache, so that we get latest to show when queried for. And also we don't want to occupy more memory with more data. That is the other reason we want to clear some entities at regular intervals.

Using a different entity manager for each unit of code won't give the advantage of loading from cache when it is revisited. If all separate EntityManagers are made to persist for the life time of application then again comes the problem with memory consumption.

So if QueryCache.Remove is working properly or RemoveEntity method automatically handles removing of only related queries from query cache, then it would solve problem of all developers who want to take care memory.

It sounds like your rather large application is using a single EntityManager for everything. That's fine for a small application, but a large application should be broken up into units of work, each one using its own EntityManager. For commonly used entities a second level cache approach can be utilized. You may wanna take a look at our reference application where you can see this in action. There is a series of videos that walk you through the code etc.

We are using Optimized QueryStrategy. So when the same query is called again we want to make use of Cache. But as the number of queries getting executed increases, number of queries in QueryCache and hence number of entities in EntityCache will also increase. 

Some of the queries, entities which were called in the start of the application will remain in the cache for the life time of application even though they are not used anymore. we want to remove those entities and queries from Cache.

And also some of the entities which were not accessed since a specific time duration, need to be removed/refreshed.

The purpose of this is to optimized utilization of memory. We have large database with lots of entities. We don't want to pile up memory with a large Cache. At the same time we don't want to miss the advantage of using cache for better performance.

This is the reason to go for manual management of Cache.

If you can suggest any alternative or any such implementation already provided by DevForce which we are not aware, then it would be really helpful for us.

Thanks

Manju

Even I tried with EntityKey as parameter to QueryCache.Remove method. This is not working too.

Is there estimated time on when the fix for this bug be available?

Thanks you

I was able to reproduce the issue. I am filing a bug and will let you know once we have a fix.

I am trying to write code to manually manage EntityManager cache. I have code which gives me the list of entities which needs to be removed from the EntityCache.

What I want to do is remove the entity form EntityCache and remove related queries from QueryCache.

DevForce provide method RemoveEntity which takes two parameters. First parameter is entity and second parameter is flag to clear query cache. If I do not provide second parameter or provide it as true, then DevForce clears the whole QueryCache, not just the queries related to the entity being removed. This is not solution for me since I dont want to remove all the queries.

Any help in this would be appreciated