[
https://issues.apache.org/jira/browse/IGNITE-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15623500#comment-15623500
]
Denis Magda commented on IGNITE-4124:
-------------------------------------
Pavel, now referring to your explanation I see how it works and how it
simplifies the troubleshooting. I've put your explanation here [1] and there
[2]. Please update it if needed. Finally, please add the table of content to
SQL page [3]. There are already a lot of sections and it's becoming more
difficult to navigate.
When you're done on your side please assign ticket on [~pgarg] for the final
review of the documentation.
[1]
https://apacheignite-net.readme.io/docs/sql-queries#troubleshooting-sql-queries
[2]
https://apacheignite-net.readme.io/v1.7/docs/troubleshooting#getting-more-insights-on-exceptions
[3] https://apacheignite-net.readme.io/docs/sql-queries
> .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: 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)
