[
https://issues.apache.org/jira/browse/IGNITE-15247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov updated IGNITE-15247:
--------------------------------------
Description:
*Motivation:*
JDBC driver must throws exceptions of java.sql.SQLException kind with a
SQLState code (XOPEN type or the SQL:2003 type).
Standard says SQLState is implementation-defined thing and define the SQLState
format, some predefined categories and ability to specify vendor-code of 'int'
type.
Vendor codes must be well-documented.
Let's map Ignite exceptions/error codes to proper SQLException with SQLState.
1. As we always know at what phase the query execution (in JDBC driver or in
SQL engine) was failed, we can use proper standard SQLState category.
2. We use IGN-XXX-nnn format (where XXX is a group name and nnn is an unique
error code within a group) [1], we can't map Ignite error code to SQL vendor
code directly.
So, we should convert non-SQL origins to IGN-SQL-nnn somehow(?) and use 'nnn'
as vendor code(?).
https://issues.apache.org/jira/browse/IGNITE-14931
was:
*Motivation:*
JDBC driver must throws exceptions of java.sql.SQLException kind with a
SQLState code (XOPEN type or the SQL:2003 type).
Standard says SQLState is implementation-defined thing and define the SQLState
format, some predefined categories and ability to specify vendor-code.
Vendor codes must be well-documented.
Let's map Ignite exceptions/error codes to proper SQLException with SQLState.
> JDBC driver for 3.0: Error handling.
> ------------------------------------
>
> Key: IGNITE-15247
> URL: https://issues.apache.org/jira/browse/IGNITE-15247
> Project: Ignite
> Issue Type: New Feature
> Components: jdbc
> Reporter: Andrey Mashenkov
> Priority: Major
> Labels: ignite-3
>
> *Motivation:*
> JDBC driver must throws exceptions of java.sql.SQLException kind with a
> SQLState code (XOPEN type or the SQL:2003 type).
> Standard says SQLState is implementation-defined thing and define the
> SQLState format, some predefined categories and ability to specify
> vendor-code of 'int' type.
> Vendor codes must be well-documented.
> Let's map Ignite exceptions/error codes to proper SQLException with SQLState.
> 1. As we always know at what phase the query execution (in JDBC driver or in
> SQL engine) was failed, we can use proper standard SQLState category.
> 2. We use IGN-XXX-nnn format (where XXX is a group name and nnn is an unique
> error code within a group) [1], we can't map Ignite error code to SQL vendor
> code directly.
> So, we should convert non-SQL origins to IGN-SQL-nnn somehow(?) and use 'nnn'
> as vendor code(?).
> https://issues.apache.org/jira/browse/IGNITE-14931
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
