[
https://issues.apache.org/jira/browse/IGNITE-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402473#comment-15402473
]
Pavel Tupitsyn edited comment on IGNITE-1915 at 8/1/16 5:52 PM:
----------------------------------------------------------------
1) We use GetOrCreateCache deliberately. If there is a user-defined cache with
specified name, it will be picked up. User has full control over the cache
configuration.
2) Having multiple databases is very unlikely, and user should understand the
consequences of using the same cache for them. Single DB is the most frequent
use case, and we want to reduce configuration efforts for it.
3) Changed to long
4) Which modes would you advise?
5) Fixed
6,7) Can you elaborate on your idea? How can EntryProcessor atomically update
two mappings (SQL->Result and EntitySet->SQL[])?
was (Author: ptupitsyn):
1) We use GetOrCreateCache deliberately. If there is a user-defined cache with
specified name, it will be picked up. User has full control over the cache
configuration.
2) Having multiple databases is very unlikely, and user should understand the
consequences of using the same cache for them. Single DB is the most frequent
use case, and we want to reduce configuration efforts for it.
3) Changed to long
4) TODO
5) Fixed
> .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.7
>
>
> 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)
