[
https://issues.apache.org/jira/browse/IGNITE-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173659#comment-15173659
]
Vladimir Ozerov commented on IGNITE-1630:
-----------------------------------------
Pavel, my thoughts on this:
3) Looks like we do not have real need for this for now. Let's remove and add
later if needed.
4) Got it. I would move it to private interface then.
5) This way some LINQ internal mechanics will be exposed to a class in Core
module. Let's handle this as a special case in LINQ module instead.
6) Should be addressed in a separate ticket.
9) Let's return just cache name then.
10) This string could be used in SQL fields query. So let's rename it to
something like "GetSqlFieldsQueryString()". Or better - return SqlFieldsQuery
with both query string and arguments set.
> .Net: Create LINQ adapter for queries.
> --------------------------------------
>
> Key: IGNITE-1630
> URL: https://issues.apache.org/jira/browse/IGNITE-1630
> Project: Ignite
> Issue Type: Task
> Components: platforms
> Affects Versions: ignite-1.4
> Reporter: Vladimir Ozerov
> Assignee: Pavel Tupitsyn
> Priority: Critical
> Fix For: 1.6
>
>
> SQL queries are one of the most frequently used features in data grids. And
> .Net comes with a very nice LINQ concept.
> * LINQ provider should come in a separate assembly
> * Make sure that assembly is included in binary distribution
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
