This question is locked. New answers and comments are not allowed.
After reading over the L2 cache documentation, I am not real sure how stored procedure or ad-hoc queries are managed in the cache? In my case, I do have a stored procedure that returns a somewhat compute intensive data set. As the data in this query is a composed from a number of tables, it was not clear to me how this type of call would be managed and ultimately refreshed in cache?
3 Answers, 1 is accepted
0
Hello Kurt,
We do not cache stored procedure or direct sql results. It is only guessable which relation this has to persistent types. Only if you use linq, oql or reference navigation the results are cached.
Kind regards,
Jan Blessenohl
the Telerik team
We do not cache stored procedure or direct sql results. It is only guessable which relation this has to persistent types. Only if you use linq, oql or reference navigation the results are cached.
Kind regards,
Jan Blessenohl
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
0
Mike
Top achievements
Rank 1
Rank 1
answered on 16 Dec 2011, 11:53 PM
Is this still the case today with the latest release? Are stored procedures and ad-hoc queries not cached? Is there a way I can get ad-hoc queries to be cached?
Thanks,
Mike
Thanks,
Mike
0
Hello Mike,
There is no way actually to cache any results of statements that OpenAccess does not produce. The problem is not the caching itself but the eviction. How can we know when we have to evict such a result? Which SP, insert , update or delete statement should make your result invalid? Even if you give us all this information, it is very easy to damage our caching and I see a high risk in supporting such functionality.
Kind regards,
Jan Blessenohl
the Telerik team
There is no way actually to cache any results of statements that OpenAccess does not produce. The problem is not the caching itself but the eviction. How can we know when we have to evict such a result? Which SP, insert , update or delete statement should make your result invalid? Even if you give us all this information, it is very easy to damage our caching and I see a high risk in supporting such functionality.
Kind regards,
Jan Blessenohl
the Telerik team
Q3’11 of Telerik OpenAccess ORM is available for download. Register for the What's New in Data Tools webinar to see what's new and get a chance to WIN A FREE LICENSE!