Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Wed, 26 Oct 2016 17:25:58 +0000 (UTC)
From: "Denis Magda (JIRA)" <jira@apache.org>
To: dev@ignite.apache.org
Message-ID: <JIRA.13015495.1477502726000.91509.1477502758517@Atlassian.JIRA>
In-Reply-To: <JIRA.13015495.1477502726000@Atlassian.JIRA>
References: <JIRA.13015495.1477502726000@Atlassian.JIRA> <JIRA.13015495.1477502726853@arcas>
Subject: [jira] [Created] (IGNITE-4124) .NET: inconvenient to debug SQL
 issue from VisualStudio output
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 26 Oct 2016 17:26:00 -0000

Denis Magda created IGNITE-4124:
-----------------------------------

             Summary: .NET: inconvenient to debug SQL issue from VisualStudio output
                 Key: IGNITE-4124
                 URL: https://issues.apache.org/jira/browse/IGNITE-4124
             Project: Ignite
          Issue Type: Sub-task
          Components: platforms
            Reporter: Denis Magda
             Fix For: 1.8


It's difficult or not clear how to debug wrong SQL queries from Visual Studio. The output simply says that the query can't be parsed.

Let's try to improve the user experience here somehow. If it's possible to get more details from Java stack trace it would be perfect. If there are some existed VisualStudio hints then let's document them on this page
https://apacheignite-net.readme.io/docs/sql-queries


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)