You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2016/03/10 14:48:40 UTC
[jira] [Comment Edited] (IGNITE-2764) LINQ plan caching
[ https://issues.apache.org/jira/browse/IGNITE-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189263#comment-15189263 ]
Pavel Tupitsyn edited comment on IGNITE-2764 at 3/10/16 1:48 PM:
-----------------------------------------------------------------
* EF walks the expression tree and generates a string key for caching
* caching can be disabled globally or for a specific query
* NH reuses ReLinq visitor to generate key, we should go the same way: https://github.com/nhibernate/nhibernate-core/blob/master/src/NHibernate/Linq/NhLinqExpression.cs
was (Author: ptupitsyn):
* EF walks the expression tree and generates a string key for caching
* caching can be disabled globally or for a specific query
> LINQ plan caching
> -----------------
>
> Key: IGNITE-2764
> URL: https://issues.apache.org/jira/browse/IGNITE-2764
> Project: Ignite
> Issue Type: Sub-task
> Components: platforms
> Affects Versions: 1.1.4
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Fix For: 1.6
>
>
> Investigate EF/NHibernate: how do they calculate cache key from expression tree to cache query plan?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)