[
https://issues.apache.org/jira/browse/IGNITE-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15436922#comment-15436922
]
Pavel Tupitsyn commented on IGNITE-1915:
----------------------------------------
We can't test EF caching in isolation, because there is a lot of EF-related
boilerplate.
For integrated testing (with real EF calling our caching layer) the options are:
* Effort https://effort.codeplex.com/. In-memory embedded DB. Not suitable
because CommandText is always null.
* SQL Server Compact - disk-based embedded DB, works with EF properly.
> .NET: Ignite as Entity Framework Second-Level Cache
> ---------------------------------------------------
>
> Key: IGNITE-1915
> URL: https://issues.apache.org/jira/browse/IGNITE-1915
> Project: Ignite
> Issue Type: Task
> Components: platforms
> Affects Versions: 1.1.4
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Labels: .net, roadmap
> Fix For: 1.8
>
>
> Entity Framework is #1 ORM for .NET
> We should provide easy solution to boost Entity Framework performance with
> Ignite.
> EF5 and EF6 have different 2nd level cache mechanisms (EF5 has a built-in
> one, EF6 requies more customization or a 3rd party lib like
> https://efcache.codeplex.com/). For now, let's do EF6 only.
> This should be in a separate assembly and a separate NuGet package.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
