[
https://issues.apache.org/jira/browse/IGNITE-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130820#comment-15130820
]
Pavel Tupitsyn commented on IGNITE-1896:
----------------------------------------
LINQ (IGNITE-1630) is coming soon, so we can close this issue, I think.
LINQ solves the same problem, and way better. Raw SQL queries will be left for
some special cases, so verbose syntax is not a big deal.
What do you think?
> .Net: Improve query API
> -----------------------
>
> Key: IGNITE-1896
> URL: https://issues.apache.org/jira/browse/IGNITE-1896
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
> Affects Versions: 1.1.4
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Fix For: 1.6
>
>
> Current API is very clumsy.
> Cache is generic, however we require the user to specify query type
> explicitly.
> There are cases when query type is a string and/or is different from current
> cache generic type, so the current API has to be kept.
> However, we should provide simple methods with generic inference:
> {code}
> IQueryCursor<ICacheEntry<TK, TV>> ScanQuery(ICacheEntryFilter<TK, TV>
> filter);
> IQueryCursor<ICacheEntry<TK, TV>> SqlQuery(string sql, params
> object[] args);
> IQueryCursor<ICacheEntry<TK, TV>> SqlQuery(string sql, bool local,
> params object[] args);
> IQueryCursor<ICacheEntry<TK, TV>> TextQuery(string text);
> IQueryCursor<ICacheEntry<TK, TV>> TextQuery(string text, bool local);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
