You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Igor Sapego (Jira)" <ji...@apache.org> on 2021/09/13 09:50:00 UTC

[jira] [Assigned] (IGNITE-15204) SQL exception to be handled by thin clients [CPP]

     [ https://issues.apache.org/jira/browse/IGNITE-15204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Sapego reassigned IGNITE-15204:
------------------------------------

    Assignee: Igor Sapego

> SQL exception to be handled by thin clients [CPP]
> -------------------------------------------------
>
>                 Key: IGNITE-15204
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15204
>             Project: Ignite
>          Issue Type: Improvement
>          Components: thin client
>            Reporter: Alexandr Shapkin
>            Assignee: Igor Sapego
>            Priority: Major
>
> It would be nice to have meaningful error descriptions (like using ODBC) instead of general ones.
> For sample, working with SQL from a thin client it's impossible to get these errors:
>  Uniq_Constraint ,Connection error,Timeout,Bind Param error,Cursor error, Prepare error,Execute error,TABLE_NOTFOUND,CACHE_NOTFOUND
>  
> Looks like the easiest way would be to wait for Ignite 3.0 release with the new thin client protocol, but I think we can make some extension to the 2.x protocol as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)