ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Tupitsyn (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-4124) .NET: inconvenient to debug SQL issue from VisualStudio output
Date Fri, 28 Oct 2016 17:11:59 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615977#comment-15615977

Pavel Tupitsyn commented on IGNITE-4124:

Denis, I've double checked: all exception information is present on .NET side. Please make
sure to check InnerException property, or use IgniteException.ToString() to unroll all nested

Not sure if we need to update documentation. This is basic knowledge. Visual Studio allows
you to examine InnerException with "View Detail..." action on the exception dialog when in
debug mode.

> .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
>            Assignee: Pavel Tupitsyn
>             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

View raw message