ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandr Shapkin (Jira)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-15204) SQL exception to be handled by thin clients [CPP]
Date Wed, 28 Jul 2021 10:13:00 GMT

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

Alexandr Shapkin updated IGNITE-15204:
--------------------------------------
    Description: 
It would be nice to have meningful 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 clint
protocol, but I think we can make some extension to the 2.x protocol as well.

  was:
It would be nice to have meningful 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


> 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
>            Priority: Major
>
> It would be nice to have meningful 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
clint 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)

Mime
View raw message